Belzareth

Making on-chain privacy usable for normal people. Dev @duskmoth_app

[Belzareth @0xBelzareth]

https://t.co/TJu5Jqn3X4

[Belzareth @0xBelzareth]

Each line in this post is a concrete engineering requirement, not a slogan.

“Fail closed”: if the screening API times out or returns something we can’t parse, the answer is no route. A timeout never counts as a pass.

“Fees in full before confirm”: the quote includes the network fee, the engine fee and our fee, and execution is rejected if the real cost would exceed what you approved.

“Trust model labeled”: every engine carries a field that says zk or tee, and the UI has to render it. A ZK pool and a hardware rollup protect different things, and you should know which one you’re using.

“Receipt on Solscan”: if we can’t hand you a signature you can check, the payment isn’t done from our side.

If a wallet flow can’t carry all four, we don’t plug into it.

[Duskmoth @duskmoth_app]

Before Duskmoth shows up inside anyone else’s wallet, a few things have to be true.

Screening has to work every time, and fail closed when it can’t. Fees have to be shown in full before the user confirms, with nothing added later. The trust model has to be labeled honestly, because a ZK pool and a hardware-based rollup are not the same thing, and users deserve to know which one they’re using. And every payment needs a receipt that can be checked on Solscan.

If we can’t meet all of that inside a wallet flow, we won’t ship it there. A rushed integration would hurt the wallet’s users and our reputation at the same time.

[Belzareth @0xBelzareth]

The “boring” fix here deserves a proper explanation, because it was the one users actually felt.

Settlement on the private rollup confirms differently from a normal Solana send. Our status checker was waiting for a receipt shape it expected, didn’t recognize the mainnet one, and left finished operations stuck on “pending.” Nothing was lost. The money had moved. The UI just didn’t believe it.

The worst way to fix that would be to mark anything old as done. We changed it so an operation only flips to confirmed when we can actually match the settlement receipt. If we can’t match it, it stays pending and you can check it yourself.

Withdrawal routing and the mobile bugs were smaller. Still beta, still small amounts. Read your receipts.

[Duskmoth @duskmoth_app]

Update on the private USDC beta, a few days in.

It’s live on mainnet as a separate panel: private sends, deposits, withdrawals and payroll in USDC, running on @magicblock private rollup. You can also load a USDC plan straight from AI Pack.

The biggest thing we fixed this week was boring but important: some completed operations kept showing as pending because settlement receipts on mainnet weren’t being recognized. That’s sorted now, along with withdrawal routing and a few mobile layout bugs.

Still beta, still small amounts. But it’s running.

[Belzareth @0xBelzareth]

Opened a Telegram for Duskmoth.

If you’ve got questions about the stack, the engines, or what’s coming next, ask me there directly. I’ll share work-in-progress before it hits X.

https://t.co/NceqTvAXwo

[Duskmoth @duskmoth_app]

Our Telegram is open

A place to talk private payments, ask questions, report bugs, and help shape what Duskmoth builds next.

→ talk directly with the dev
→ early looks at what we’re testing
→ feedback that actually shapes the roadmap

Join the discussion 👇
https://t.co/mvkBOqBQPh

[Belzareth @0xBelzareth]

Dev log: where Duskmoth’s infra is now, and where I’m taking it 🛠

Today
→ wallet signs every tx, unsigned txs verified client-side
→ AI Pack writes plans, never signs
→ screening fails closed, Moth Pass checked before execute
→ router picks the engine by asset: ZK pool for SOL, @magicblock private rollup for USDC (beta)
→ backups, cross-tab lock and check-only recovery so nobody gets paid twice

Next (exploring)
→ single-signature batches: N payments, one approval
→ split and timed payouts for payroll
→ a Route API so wallets can offer Duskmoth routes natively
→ multisig approval + more engines as they hit mainnet
The flow stays the same. The engines underneath get better.
I’ll post progress as each piece ships.

[Belzareth @0xBelzareth]

Spent the week shipping the MagicBlock beta. Here’s the full write-up of how it all fits together: the router, both privacy engines, and the recovery logic that stops double payments.

Questions welcome, I’ll answer in the replies 👇

[Belzareth @0xBelzareth]

https://t.co/TJu5Jqn3X4

[Belzareth @0xBelzareth]

This is the flow I’ve been sketching for Duskmoth payroll 👇

Start on mainnet → run privately → settle on mainnet, with one signature from the user.

Duskmoth handles the part people actually see: the plan, screening, full fees and one approval. A private rollup handles execution: split payouts, timed releases, settled back on Solana.

Exploring it now. Will share what works and what doesn’t.

[MagicBlock ✨ @magicblock]

MagicBlock v1.0 is live on Solana after a year and a half of building

Apps can run in real time, prove every outcome is fair, and keep payments private, without leaving Solana

Read the full Validator v1.0 release: https://t.co/Wb3vjQ0CUt