Duskmoth docs

Overview

Duskmoth is a chat interface for private transfers on Solana. You type what you want in plain words, Duskmoth shows a readable preview, and your own wallet signs. Under the hood it uses the Privacy Cash shielded pool on mainnet, so the recipient gets paid without an on-chain link back to your wallet.

Duskmoth is non-custodial. It never holds keys or funds, and the AI can only propose a transaction. Every move needs your wallet's signature.

Quickstart

1. Open the app and connect Phantom, Solflare or Backpack. Your wallet must be on Solana mainnet.
2. Sign once to unlock your private balance. Your wallet asks you to sign the message Privacy Money account sign in. This is free, moves nothing, and lets your browser derive the key that encrypts your private notes.
3. Say what you want, for example send 0.5 SOL to 7xKp…sMn privately.
4. Read the preview: amount, fees, what the recipient receives, privacy strength, and the screening result for both addresses.
5. Confirm and sign. Your browser builds a zero-knowledge proof, the deposit goes on-chain, and a relayer pays the recipient from the pool.

Start with a small amount, such as 0.05 SOL, the first time you use it. Withdrawals have a flat fee, so very small sends are expensive (see Fees).

How a private send works

For Shield now, send later, steps 4 and 5 happen whenever you choose. The longer the gap and the rounder the amount, the more deposits yours blends into.

Network and addresses

Duskmoth runs only on Solana mainnet-beta. All values below are the ones in the Privacy Cash SDK version Duskmoth ships (privacycash@1.3.1). Verify them on any explorer before you trust them.

Explorer: view the program on Solscan.

Wallet activity

When you connect a wallet, the Wallet panel reads its public history straight from Solana mainnet, so you can see exactly what anyone with an explorer can see.

Transactions that touch the Privacy Cash program are labelled Shielded or Private payout based on the sampled transaction data. Unavailable details are marked unavailable. There is no demo wallet or sample activity fallback.

Fees and limits

The relayer publishes its current rates at https://api3.privacycash.org/config (withdraw_fee_rate, rent_fees, minimum_withdrawal), and the SDK reads them at send time. The preview always shows the live numbers. Rent fees and minimums for SPL tokens such as USDC are set per token in that same config.

Worked example

Duskmoth limits

• Maximum per send: 5 SOL or 500 USDC by default. Hosts can change this with MAX_SEND_SOL and MAX_SEND_USDC.
• Supported tokens in the app: SOL and USDC. The pool supports more SPL tokens, which may be added later.
• The relayer enforces a minimum withdrawal per token (for SOL, currently 0.01 SOL).

What you can say

Write in plain English. With a Claude key on the server, phrasing is flexible. Without one, a rule-based parser handles the patterns below.

The recipient must be a full Solana address that you typed or pasted yourself. The server rejects any address the AI produced that is not in your message, word for word.

Sanctions screening

Duskmoth checks the recipient and any supplied sender using Scorechain's sanctions-only API. Missing senders are not claimed as checked. These checks do not enable live transfers.

GET https://sanctions.api.scorechain.com/v1/addresses/<ADDRESS>
x-api-key: <SCORECHAIN_API_KEY>

• Scorechain returns a boolean sanctions-list match, not a risk score.
• A match blocks approval. A no-match result is not proof that funds are safe.
• Fails closed: invalid addresses, missing credentials, invalid provider responses, request limits, and network failures cannot pass.
• The free service is limited to 100 lookups/hour and non-commercial use. Solana list completeness and public commercial eligibility still need confirmation.

Automated match tests use clearly labelled provider fixtures. They are not evidence of a verified live sanctioned Solana address.

Privacy score

The score reads what the public chain already says about a wallet, using the Helius Wallet API. To stop people from profiling other wallets, you must prove ownership first by signing this exact message (valid for 5 minutes, ed25519):

Duskmoth: prove I own <ADDRESS> to see my privacy score. Timestamp <UNIX_MS>. This costs nothing and moves no funds.

The score starts at 100 and is graded A to F. The share card shows only the score and grade, never the address or balance.

Helius serves identity, batch-identity and funded-by only on paid plans (free plans get 403). On a free key, those signals are skipped.

API reference

The Duskmoth server is a small Express app. Base path /api, JSON in and out, rate limited per IP (about 40 requests per burst). Request bodies and addresses are never logged.

{ "ok": true, "mode": "production", "network": "mainnet-beta", "ai": "claude",
  "screening": "scorechain", "screeningScope": "sanctions-only", "data": "helius", "liveSend": true, "demoWallet": false, "relayerProxy": true }

{
  "ai": "claude",            // or "rules"
  "screening": "scorechain", // or "off"
  "data": "helius",          // or "public-rpc"
  "liveSend": true,          // user confirmation and wallet approval required
  "limits": { "SOL": 5, "USDC": 500 }
}

// request
{ "message": "send 0.5 SOL to 7xKpQm3vHsT9wRb2eYcNf4LdJ8gUaZ5qXr6tPkW1sMn privately" }
// response
{
  "reply": "Ready to send 0.5 SOL to 7xKp…1sMn without linking it to your wallet…",
  "action": { "type": "send", "amount": 0.5, "token": "SOL",
              "recipient": "7xKpQm3vHsT9wRb2eYcNf4LdJ8gUaZ5qXr6tPkW1sMn", "delay": "now" }
}
// action.type: "send" | "shield" | "balance" | "score" | "help", or action is null when more info is needed

// request
{ "sender": "<ADDRESS>", "recipient": "<ADDRESS>" }
// response
 { "source": "scorechain", "scope": "sanctions-only", "allowed": true,
   "sender": { "isSanctioned": false }, "recipient": { "isSanctioned": false } }
// blocked: "allowed": false plus a "reason" string

// request
{ "address": "<ADDRESS>", "ts": 1793414400000, "signature": "<base58 ed25519>" }
// response
{ "wallet": "7xKp…1sMn", "score": 62, "grade": "C", "source": "helius", "txCount": 418,
  "signals": [ { "id": "cexFunded", "label": "Funded from an exchange", "impact": -25, "detected": true, "fix": "…" } ],
  "summary": "Your wallet scores 62/100 (C). The biggest leaks: …",
  "fixes": [ "…" ] }
// 401 if the signature is missing, wrong or older than 5 minutes

// request
{ "address": "<ADDRESS>" }
// response
{ "address": "…", "network": "mainnet-beta", "source": "helius-rpc",
  "sol": 4.218, "usdc": 120.5,
  "stats": { "sampled": 100, "last30d": 23, "activeDays30d": 9, "failed": 1,
             "lastActive": 1793410000, "oldestSampled": 1781000000 },
  "history": [ { "signature": "…", "time": 1793410000, "ok": true, "type": "receive",
                 "sol": 0, "usdc": 25.5, "fee": 0 } ] }

Self-host on mainnet

Requirements: Node.js 20+ or Docker, and a domain with HTTPS (browser wallets will not sign on plain HTTP outside localhost). The release package already contains the ZK circuit and the pre-built proving module. Full steps are in INSTALL.md.

cp .env.example .env      # fill in your keys and domain
docker compose up -d --build
docker compose exec duskmoth npm run check

# or without Docker
npm ci && npm run build
npm run check              # connectivity checks: mainnet RPC, relayer, Scorechain, Helius
pm2 start ecosystem.config.cjs

Production environment

NODE_ENV=production
PORT=8787
PUBLIC_URL=https://duskmoth.xyz

ENABLE_LIVE_SEND=true        # enable wallet-approved transfers; false is an operator kill switch
MAX_SEND_SOL=1               # start low
MAX_SEND_USDC=100
RELAYER_PROXY=true           # browser → /api/relayer → official relayer
RELAYER_URL=https://api3.privacycash.org

SCORECHAIN_API_KEY=…         # sanctions-only checks
HELIUS_API_KEY=…             # mainnet RPC + Wallet API
ANTHROPIC_API_KEY=…          # optional
ANTHROPIC_MODEL=claude-sonnet-5-5

ALLOW_DEMO_WALLET=false
ALLOW_UNSIGNED_SCORE=false

In production Duskmoth never shows invented data: when a service is missing or down, the feature says so and stops. GET /api/health reports which services are live.

Go-live checklist

• npm run check ends with All required checks passed.
• GET /api/health shows "mode": "production", "screening": "scorechain", "data": "helius", "liveSend": true, "demoWallet": false. Enabled does not mean a live-funds test has passed.
• Send 0.05 SOL to a second wallet you own. Confirm the deposit and the relayer withdrawal on Solscan, and confirm no direct link between the two wallets.
• Obtain a provider-supported sanctioned Solana test case and verify it is blocked; do not assume an old Range example is sanctioned by Scorechain.
• Lower MAX_SEND_SOL and MAX_SEND_USDC for your first days live.
• Check that privacy tools are legal where you and your users are.

Security model

• API keys (Anthropic, Scorechain, Helius) live only on the server. The browser talks to Helius through /api/rpc with a method allowlist. Transaction submission is blocked while transfers are unavailable.
• No request bodies or addresses are logged. The only thing written to disk is the waitlist email file.
• Losing access to your wallet means losing access to your private notes too, because the encryption key is derived from your wallet's signature. Withdraw what you do not need to keep shielded.

Honest limits

• The anonymity set is what other people deposit. If you deposit 3.217 SOL and someone receives 3.206 SOL a minute later, the amounts and timing can link you. Use round amounts and wait.
• Privacy is not invisibility. Your deposit is still visible as a deposit into the pool.
• Third-party dependence. Wallet features depend on Helius/RPC and sanctions checks depend on Scorechain. No failed service is replaced with invented data. Wallet-approved transfers depend on successful screening, current relayer fees, sufficient funds, proof generation and network confirmation. Provider coverage, commercial-use eligibility and live-funds verification are separate requirements.
• The live send path is new. Test it with small amounts on mainnet before relying on it.
• Not legal or financial advice. Privacy tools are restricted in some countries.

FAQ