₿₳₹₮ Moonkey intern #7

Not a roadmap. A changelog. Everything we’ve shipped in the last two weeks is either usable or checkable today. No “soon”, no teaser. → Moth Pass, rebuilt. Burn $DMOTH and get a pass. One pass covers one AI Pack plan or one Payroll batch. Passes use blind signatures, so a pass can’t be tied back to the burn that created it. → AI Pack with USDC plans. Describe what you want, see the full cost, approve it yourself. → Private Payroll. Up to 20 recipients per batch. You can refresh and resume, and nobody gets paid twice. → Private USDC in mainnet beta, built on MagicBlock’s private rollup. → 3,000,000 $DMOTH burned for real with BurnChecked. Check it on Solscan. → SDK v0.2.0, public on GitHub. Six things in two weeks from a small team. Every one has an honest label: live, beta or on-chain. This is the pace we plan to keep.

Two requests keep coming in. One is “can payroll just run every month?” The other is “can my agent pay for things?” Both are on the research list. The rule we’re keeping for both is that the prep can be automated, but the approval can’t. For recurring payroll, we’re looking at Solana’s Subscriptions & Allowances program for monthly schedules. Duskmoth prepares that month’s plan with recipients, amounts, the maximum upfront cost and the engine. For agent payments, Pay.sh gives AI agents a payment rail. An agent can request a payment, and Duskmoth turns the request into a plan. Both paths end the same way. A human reviews it, can edit or cancel it, and approves it. Then the wallet signs and the payment settles. The agent prepares, a human approves, and the wallet signs. Nothing goes out on autopilot, and nothing is resent without you. This fits what AI Pack already does with $DMOTH Moth Pass today. It just adds schedules and agents as new ways a plan can start. Exploring, no dates.

Two smaller pieces we’re researching, both about making a plan less fiddly. The first is swap, then pay. Say you hold SOL and the recipient wants USDC. Today that’s two separate steps in two separate places. The idea is one reviewed plan: a Jupiter route with the rate, slippage and fee shown upfront, then a private USDC send through the routed engine, all under one approval and one receipt. The second is checking without seeing, which is research only. Arcium runs computation on encrypted data with MPC. One example we’re thinking about: checking a payroll batch for totals, limits and duplicates without salaries ever being readable on our server. The Arcium part stays research until the use case and the cost both make sense. We’d rather say “not yet” than ship a demo nobody needs. @JupiterExchange @Arcium

What comes after MagicBlock: the privacy stack we’re researching for Duskmoth Right now Duskmoth runs two engines. @theprivacycash covers SOL through a ZK shielded pool, and MagicBlock’s Private Ephemeral Rollup covers USDC in mainnet beta. Two engines is a start, not the finish. The thing we care about most is never depending on one protocol. When deposits paused on one engine, the app kept working because the router had somewhere else to go. That’s the design: you pick the payment, the router shows you which engine fits, what it hides, what it trusts and what it costs, and you approve. Here’s what we’re exploring next. None of it is live in Duskmoth yet, and there are no dates. @Helius Privacy (Rings). A ZK UTXO layer that can hide sender, recipient, asset and amount, settling in one Solana transaction. We already run on Helius infrastructure, so this one fits naturally. It’s still devnet-only, with mainnet gated on audits and formal verification of the circuits. We’ll build against devnet and only switch it on for real money once that work is done. @cloak_ag . A ZK pool covering SOL, USDC and USDT. Two things matter for us here: USDT support, and viewing keys, so a business can open its own records to an auditor without opening them to everyone. We’re evaluating it carefully, including its audit status. Token-2022 Confidential Transfers. Encrypted balances and amounts. To be clear about the limits: sender, recipient and timing stay visible. It could still be useful for payroll where the only goal is keeping salaries private. It depends on stablecoin issuers turning it on. Squads. A team payroll batch shouldn’t hang on one person’s click. The plan is that one member prepares the batch, the team multisig approves it, and then it executes privately. Recurring payments and agent rails. Solana’s Subscriptions & Allowances program for monthly payroll schedules, and Pay.sh for AI agent payments. The rule doesn’t change for either: the agent prepares, a human approves, the wallet signs. Our SDK never signs for you. @Arcium and Jupiter. Arcium is research only for now: encrypted checks, such as validating a payroll batch without exposing amounts. Jupiter is for swap-then-pay inside a single reviewed plan. What stays the same across every engine: → screening at the edge, which fails closed → the engine and its trust model shown before you approve → no silent rerouting, and nothing resent without you Privacy on Solana is a spectrum, not a switch. ZK, TEE and encrypted amounts each protect different things. Our job is to tell you which one you’re using, honestly, every time. Not an anonymity guarantee. Sanctions-list screening, not full AML. Start small. duskmoth.xyz

Duskmoth Payroll is live in beta: up to 20 recipients per batch, with confirmed, pending and uncertain states. An uncertain payout is never resent automatically. What we hear from teams and DAOs is that a payroll batch shouldn’t depend on one person’s click. So we’re exploring Squads multisig for the approval step: One member prepares the batch. Duskmoth validates and screens every address. If anything is flagged, nothing moves. The team’s Squads multisig approves at its threshold, for example 2 of 3. The batch executes privately through the routed engine. Receipts come back per recipient. Every signer sees the same reviewed plan and the same full cost before anything moves. Nobody approves a number they didn’t see. The SDK still never signs for anyone. Moth Pass works the same way: one pass per Payroll batch, from burning $DMOTH. The multisig step is exploring, not shipped.

Duskmoth is now open source. Fork the code, explore how it works, and contribute. Application Wallet-approved private transfers on Solana, Moth Pass, AI Pack, and Private Payroll. Fork it to run your own instance, improve wallet support, or contribute fixes. github.com/duskmoth-dev/dusk… SDK Integrate with Duskmoth’s HTTP APIs. No wallet signing or transaction broadcasting. github.com/duskmoth-dev/dusk… Documentation Setup, usage, API references, and privacy limitations. github.com/duskmoth-dev/dusk… We also forked two ecosystem repositories to submit focused contributions: • Electric Capital add Duskmoth SDK and docs to the Solana taxonomy: github.com/electric-capital/… • Awesome Solana OSS add Duskmoth SDK under Web Tooling: github.com/StockpileLabs/awe… Both submissions are awaiting maintainer review not confirmed listings or endorsements. Bug reports, useful improvements, and focused PRs are welcome.

One gap in Duskmoth’s engines is obvious: USDT. Another keeps coming up in business conversations: “fine, private, but how do I show my accountant?” That’s why we’re evaluating Cloak. Cloak is a ZK pool for SOL, USDC and USDT. The part we care about is viewing keys. A business can pay its team privately, so the public sees the pool and not the payment. Later, the business can hand an auditor read-only access to its own records. The auditor can read, but can’t spend or move anything. It’s selective disclosure, and the owner decides who sees what. Cloak also screens at the edge through Range, which lines up with how Duskmoth already works. What we’re weighing before anything ships: → the audit report isn’t public yet → the pool is still small, and pool size affects your cover → they run their own payroll product too If it passes, it would show up in Duskmoth as its own engine with its own label. It wouldn’t be blended in quietly.

“Private” means different things depending on the engine, and it’s worth being precise about it. ZK pools (Privacy Cash, and Helius Rings and Cloak on the research list) break the link between sender and recipient and hide amounts inside the pool. What you trust is the math and the audited circuits. Your cover depends on how many other people use the pool. A TEE rollup (MagicBlock PER) processes transfers privately inside Intel TDX hardware. It’s fast and cheap, and it’s good for USDC. What you trust is the hardware. Deposits and withdrawals are still visible onchain. Encrypted amounts (Token-2022 Confidential Transfers) encrypt balances and amounts, and that’s all. Sender, recipient and timing stay visible. That’s useful for keeping salaries private, but it isn’t anonymity. None of these is “the best one.” They protect different things. That’s why Duskmoth shows which engine you’re on and what it trusts before every approval. You shouldn’t have to read docs to know what’s hidden and what isn’t.

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.

The engine we’re watching most closely right now is Helius Privacy, built on Solana Rings. Here’s how it works. You get a shielded keypair with signing, nullifier and viewing keys, all created on your side. You register it onchain so people can pay you privately. You deposit, the funds become private notes, and private transfers then hide the sender, the recipient, the asset and the amount. When you’re done, you withdraw back to any Solana address. Helius never holds your spending keys. That part matters to us. It fits naturally because Duskmoth already runs on Helius infrastructure. The plan is a HeliusRingsAdapter that uses the same router interface as our live engines, sits behind a feature flag, and runs on devnet first. The honest part: Helius’s own docs say it’s beta and devnet only. Mainnet waits on three audits and formal verification of the ZK circuits. So no real money goes through it in Duskmoth until that work lands. We won’t rush someone else’s audit for a launch post. Longer term, Custom Rings could give business payroll its own policy and compliance controls. @Helius The engine we’re watching most closely right now is Helius Privacy, built on Solana Rings. Here’s how it works. You get a shielded keypair with signing, nullifier and viewing keys, all created on your side. You register it onchain so people can pay you privately. You deposit, the funds become private notes, and private transfers then hide the sender, the recipient, the asset and the amount. When you’re done, you withdraw back to any Solana address. Helius never holds your spending keys. That part matters to us. It fits naturally because Duskmoth already runs on Helius infrastructure. The plan is a HeliusRingsAdapter that uses the same router interface as our live engines, sits behind a feature flag, and runs on devnet first. The honest part: Helius’s own docs say it’s beta and devnet only. Mainnet waits on three audits and formal verification of the ZK circuits. So no real money goes through it in Duskmoth until that work lands. We won’t rush someone else’s audit for a launch post. Longer term, Custom Rings could give business payroll its own policy and compliance controls.

If you could send privately from your wallet with one switch, what would you actually use it for? Paying a freelancer? Sending to family? Moving funds between your own wallets? Paying a team? We’re shaping the wallet-native route around real answers, not guesses. Reply here or come talk to us directly in Telegram, where the dev answers questions himself 👇 t.me/duskmoth_app

A small detail about payroll that took more work than any feature. If your browser closes halfway through a batch, what happens? On Duskmoth, every payment is saved as it goes. When you come back, you see what’s confirmed, what’s left, and you continue from there. If a payment is uncertain, we don’t guess. You get a “Check” button that looks it up first. It will never be resent automatically. We also added cross-tab protection, so opening the app in two tabs can’t overwrite a saved batch. Nobody tweets about this kind of thing, but it’s the difference between a demo and something you’d trust with salaries.

Payroll in USDC, without publishing everyone’s salary. Private USDC payroll is live in beta on Duskmoth. Approve once, settle on Solana. Join the beta 👉 t.me/duskmoth_app

Duskmoth Changelog: MagicBlock Mainnet Beta 🦋 Private USDC payments are now in beta, powered by MagicBlock’s Private Ephemeral Rollup. Added • Dedicated MagicBlock USDC panel: private sends, deposits, withdrawals & Payroll • Load USDC payment plans straight from AI Pack • Maximum upfront cost review: network, program & account setup fees • Transaction backups + Check-only recovery for unresolved payments Fixed • Withdrawal routing & mainnet settlement receipts • Completed operations no longer stuck as pending • Cross-tab protection for saved operations • Mobile overflow, keyboard access & stray null text Privacy here runs on trusted hardware (TEE), a different model from our ZK pool. Beta, so start small. 🔗 duskmoth.xyz

UPDATE : Duskmoth SDK v0.2.0 is now available. Developers can integrate Moth Pass issuance and redemption, AI Pack planning, and Private Payroll authorization through our dependency-free JavaScript/TypeScript HTTP client. This release adds typed premium APIs, operation-specific timeouts, and recovery guidance for interrupted requests. The SDK does not hold private keys, sign transactions, or send payments. Premium API calls can consume Moth Passes. Source, installable package, and release notes: github.com/duskmoth-dev/dusk…

Five things to know about Duskmoth this week 🦋 01. Payroll recovery: refresh and resume, no double payments 02. Status: new deposits paused at the protocol level, everything else running 03. AI Pack: one sentence becomes a payment plan you review 04. Moth Pass: one pass = one AI plan or one payroll batch 05. Privacy score: see what strangers can learn from your wallet duskmoth.xyz

Payments that don’t leave a map. Screened, non-custodial, verifiable on Solscan. Duskmoth: private payments on Solana. Start small.

“Pay them in USDC.” “But I only hold SOL.” That gap is where most payment plans fall apart. AI Pack already turns plain-English instructions into SOL or USDC payment plans. What we’re exploring next is handling the swap inside the same plan: → you say what you want to pay → the plan shows the swap needed first → you see the rate, fees and final amounts → you approve once Jupiter is the natural place to look for swap routing on Solana, and it’s on our research list. The AI still never moves funds. It only writes the plan you review.