cryocor

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