
Private sends on Solana. Screened, non-custodial. $DMOTH CA: 9ueEeBuYUc9X1GrNCyWHbKGnHJq1kaD2nvDapDsMpump
Joined October 2026
- Tweets168
- Following29
- Followers231
- Likes126
Pinned Tweet
Moth Pass has been updated. AI Pack and Private Payroll are now available on Duskmoth.
AI Pack 1 pass per generated plan Turn your instructions into a SOL or USDC payment plan. Review the recipients and amounts before using it AI does not move your funds.
Private Payroll 1 pass per batch Pay up to 20 recipients from your existing private balance through Privacy Cash. Review fees and recipient amounts before running the batch. Confirmed payments are not repeated when you resume.
Burn $DMOTH to get Moth Passes. Passes are optional Duskmoth’s core sending, shielding, and withdrawal features remain available without them.
Three balances. Not interchangeable.
Your public wallet is visible to everyone. Your private balance holds funds you’ve shielded. Your Moth Pass balance is premium credits in your browser, and it isn’t money.
Shield moves public → private. Withdraw moves private → recipient. Burning $DMOTH turns into passes, one way.
Seeing “insufficient”? Check which balance it means first. Don’t deposit again just to refresh it.
duskmoth.xyz/app
Duskmoth Payment Requests: paste your address, pick SOL or USDC, set the amount. You get one link and one QR.
Creating it signs nothing. Opening it sends nothing. The payer checks the details and decides in their own wallet.
duskmoth.xyz/request
What has to be true before the MagicBlock route opens more broadly:
resolve two older submissions whose outcomes are still uncertain
complete the remaining batch-verification requirements
test wallet approval through the browser
reconcile estimated costs against actual results
complete the release security review
The three-recipient mainnet Payroll test is done. On its own, that doesn’t mean the route is ready for unrestricted public use.
We’ll post completed changes with evidence, and keep them clearly separate from what’s still planned.
We want Duskmoth’s implementation to be easy to inspect and easy to build on.
Planned GitHub updates:
→ tested SDK changes, released with test results
→ practical examples
→ compatibility notes
→ contribution guidance
We also plan to document how the MagicBlock route works in Duskmoth, what has actually been verified on mainnet, and what limits remain.
Using @magicblock technology doesn’t imply an official partnership or endorsement. It’s integration work, and we’ll describe it that way.
Planned improvements to Payment Requests are about clarity, not automation.
The goal: when you open a request, you should understand right away
→ the receiving address
→ the token
→ the amount
→ the ways you can pay it
And one rule that doesn’t change: opening a request link must never sign or send a transaction.
A request asks for a payment. It doesn’t take one. The payer stays in control of whether to pay, and how.
duskmoth.xyz/request
AI Pack turns plain words into a payment plan. Payroll runs it. The plan is to make the step in between much clearer.
Before you approve anything, these should stay visible in one place:
→ every recipient
→ every amount
→ estimated fees
→ the payment route that will be used
Same rule as always: an AI-generated plan is a draft, not permission to move funds. You review it, you approve it, and your wallet signs.
The handoff is the moment where mistakes are cheapest to catch, so that’s where we’re putting the work.
Where should Duskmoth go next?
With Requests, Activity, the Developer Hub and the Security page out, these are the proposed priorities. They focus on making what exists easier to understand and verify.
1. Clearer recovery states. Make it obvious whether an operation is waiting, unknown, partial or actually done.
2. Better release evidence. Say plainly which checks used simulated responses, which used real funds, and what’s still unverified.
3. More developer examples. Build on the offline SDK example: unavailable services, interrupted requests.
4. Mobile and accessibility. Keep improving the screens where you check addresses, amounts and fees.
Separately, MagicBlock USDC stays in internal beta until its acceptance requirements are met.
These are proposals, not a claim that work has started. No dates, no new partnerships.
What would you put first? Reply with a number.
github.com/duskmoth-dev
You shouldn’t need to risk real money to contribute to a payments project.
So the plan is a MagicBlock-focused example for contributors. It would prepare payment requests and read simulated statuses, and it needs:
→ no funds
→ no credentials
→ no wallet signing
→ no live transactions
Simulation examples and mainnet examples will be clearly separated, so you always know which one you’re running and what you’re actually testing.
It builds on the offline browser example already in SDK v0.2.2.
On the SDK side, the plan is to make Duskmoth’s responses for @magicblock transactions much more explicit: status, cost estimates and recovery.
The core problem we want to solve: three different events often get treated as one.
the transaction was submitted
the source funding was confirmed
the recipient was actually paid
They aren’t the same thing, and an integration that confuses them will eventually tell a user “done” when it isn’t. The SDK should make that impossible to mix up.
This work builds on our completed three-recipient mainnet Payroll test. Here’s one confirmed test payout from that run, finalized on Solana:
solscan.io/tx/HdZehdQ4gESYwX…
What we’re working toward next at Duskmoth.
The next phase isn’t about new features. It’s about making the payment infrastructure we already have easier to integrate, easier to understand, and easier to recover when a connection drops mid-payment.
What’s planned:
→ clearer MagicBlock responses in the SDK
→ contributor examples that run with no funds
→ a clearer review step from AI plan to Payroll
→ clearer payment requests
→ updated technical docs
Broader MagicBlock access still depends on the remaining verification checks. We’ll publish each change with evidence once it’s done, and keep it separate from what’s still planned.
Your wallet is louder than you think.
Every payment on Solana is public: who you paid, how much, and when.
Here’s the full Duskmoth walkthrough, filmed on the live app:
→ connect your wallet. Keys stay in it
→ shield, send or withdraw in plain words
→ request a payment with a link or QR
→ keep an optional local journal
→ get Moth Passes, run AI Pack and Payroll
→ read the developer and security pages
Every step shows the real screen and what to check before you approve. It also covers what to do when something gets interrupted, so you never pay twice.
Start small, read the preview, and decide for yourself.
duskmoth.xyz
Duskmoth × MagicBlock Mainnet Payroll Verified
Duskmoth’s USDC payment route built with @magicblock has completed a real three-recipient payroll test on Solana mainnet.
What we verified: • Three payments with different amounts, each confirmed at its recipient.
• One existing Moth Pass used for the entire batch—not per recipient.
• Stop-and-resume recovery without repeating the first payment.
• Observed source costs stayed within the reviewed limits.
On-chain payment proofs:
① solscan.io/tx/HdZehdQ4gESYwX…
② solscan.io/tx/PWZeCMsR7GgzaV…
③ solscan.io/tx/KaHgXHQkRrDU2f…
MagicBlock adds a separate USDC route alongside Duskmoth’s existing Privacy Cash integration.
Status check on MagicBlock USDC: it’s still an internal mainnet beta for allowlisted wallets.
What exists: a separate workflow for wallet-approved USDC send, deposit, withdraw and Payroll, with its own operation and recovery context. It’s an additional engine, not a replacement for Privacy Cash.
Before we open it to everyone, the remaining work has to show results:
→ funded Payroll acceptance testing completed
→ at least 10 successful internal mainnet batches
→ zero duplicate or lost payments in that set
→ fee accuracy and recipient settlement verified
→ remaining release-readiness findings resolved
One distinction we hold ourselves to: “source confirmed” doesn’t mean “recipient paid”. Settlement has to be proven.
duskmoth.xyz/tools
Duskmoth uses different technologies for different jobs. Mixing them up leads to wrong assumptions, so here’s who does what:
Privacy Cash provides the shielded SOL and USDC route.
Helius handles public-chain data and RPC.
Scorechain checks addresses against sanctions lists. It’s not an AML risk score and not an anonymity certificate.
Anthropic powers AI planning. A plan is a draft for you to review. The AI can’t move funds.
MagicBlock is a separate USDC engine, still in internal beta. It doesn’t replace the Privacy Cash balance.
Moth Pass gates optional premium actions. The token behind it is an ordinary public SPL token, not a privacy coin.
None of these names is a guarantee. No provider, privacy score or health check proves a payment was anonymous or settled correctly. That’s why every payment still ends with your own review and your own signature.
What does a Moth Pass actually do?
It unlocks optional premium actions. That’s it. You don’t need one to shield, send or withdraw.
Current uses:
→ AI Pack: 1 pass per generated plan. A plan is a draft and moves nothing
→ Private Payroll: 1 pass per batch, not per recipient. Up to 20 people
→ Split withdrawal: 1 pass for the operation, with relayer fees per part
→ Pre-withdraw privacy check: free
A plan and the payroll batch that runs it are two separate actions, with two separate passes.
You get passes by burning $DMOTH. The burn is public and permanent. The tokens are destroyed, not sent to a team wallet.
Two habits that matter:
tap Back up passes right after a burn. A usable backup is a bearer secret, so treat it like cash
if issuance stops after the burn, use Resume purchase. Never burn again
duskmoth.xyz/pass
Three commands, three different jobs:
shield 0.03 SOL
Moves funds from your wallet into your private balance. This doesn’t pay anyone.
send 0.03 SOL to <address> privately
Funds from your wallet, then pays the recipient.
withdraw 0.03 SOL to <address>
Pays from a private balance you already have. No new deposit.
Before you approve, read three things: the recipient, the fees, and recipient gets. Fees come out of the gross amount.
Now the rule. If a send’s deposit succeeds but the payout doesn’t finish, don’t run the whole send again. Part of your money is probably already in your private balance. Check it, then use withdraw.
An interrupted page and a failed payment aren’t the same thing. “Unknown” means go and check, not try again.
duskmoth.xyz/app
Most privacy apps tell you what they protect. Very few tell you what they don’t.
We put both on one page.
duskmoth.xyz/security covers:
→ which provider receives which data
→ why a payment-request link is not an encrypted message
→ why a public burn, timing and amounts can still say something about you
→ why pass backups and payroll exports should be treated like secrets
→ why a privacy score is an estimate, not a certificate
→ how to report a vulnerability privately
The idea is simple. If you know where your data goes, you can decide what to share, what to back up, and what to double-check before you approve.
Open code means you can inspect it. It doesn’t mean it’s been independently audited, and we say so.
Private reports: github.com/duskmoth-dev/dusk…
Never include a private key, seed phrase or pass backup in a report.
One thing confuses new users more than anything else: Duskmoth has three different balances, and they aren’t interchangeable.
Public wallet balance. The SOL and tokens in your connected wallet. Visible to everyone.
Private balance. Funds you’ve shielded through the Privacy Cash route. It shows up after the correct wallet unlock and a balance scan. Payroll pays from here.
Moth Pass balance. Premium credits stored in your browser. They aren’t SOL, they aren’t USDC, and you can’t spend them as money.
And one more rule: an experimental engine like MagicBlock keeps its own separate balance. Funds in one engine aren’t automatically available in another.
If something says “insufficient”, check which of the three it’s talking about before you deposit anything again.
Two days ago we listed two open SDK tasks. Both shipped in v0.2.2.
Typed responses. health(), config() and relayerConfig() now return clear TypeScript types. If a field doesn’t come back, it stays “unknown” in the types, never quietly treated as “ready”. Your app shouldn’t assume a feature exists because a field went missing.
Offline browser example. A page plus a mock API on one localhost address. It covers five scenarios: available, disabled, missing fields, HTTP 503 and broken JSON. No wallet, no credentials, no transactions.
npm run example:browser → open 127.0.0.1:8788
✓ 38 tests on Node 22 and 24
✓ strict TypeScript checks pass
✓ release archives scanned for credentials, checksums match
Distributed through GitHub Releases, not npm, and not audited.
Everything’s on the new Developer Hub: duskmoth.xyz/developers
Release: github.com/duskmoth-dev/dusk…
Private payments raise a practical problem: how do you keep your own records without handing them to someone else?
Local Activity is our answer. It’s an optional journal stored only in your browser.
Turn it on, and the operations you run in Duskmoth get recorded:
→ filter by type and status
→ search by address, amount or signature
→ export or import JSON
→ check a recorded signature against the chain, read-only, without resending anything
It starts off. It doesn’t scan your past. It only records what happens after you opt in, on this browser.
Two honest limits:
a journal entry is a local record you can edit, not a receipt or proof of payment
“signature confirmed” doesn’t prove who got paid or how much
Exports can contain addresses and amounts, so keep them private.
duskmoth.xyz/activity













