Integration checklist

Use this checklist when integrating against the current Devnet release:

1. Pin @lethenymous/[email protected] and connect to Solana Devnet with finalized reads where the SDK requires them.
2. Use the official program ID and a pool's actual classic SPL Token mints.
3. Provide a wallet adapter with signTransaction; private proof operations also require signVersionedTransaction.
4. Configure a validated v0 LUT. The SDK refuses private proof transaction preparation without it.
5. Derive shielded keys from a secure seed and use a durable encrypted EncryptedFileNoteStore; do not use InMemoryNoteStore for persisted funds.
6. Supply the authenticated ProductionProver binary and exact production PK files for the relevant circuits.
7. Check the complete signed transaction against the 1,232-byte cap and use an appropriate slippage minimum.
8. If relaying, prepare only a supported private_swap or unshield v0 message and never send a wallet secret to the relayer.
9. Poll the returned signature and treat unknown as unresolved. After restart, call reconcilePending() before selecting notes.
10. Back up the encrypted note journal and its seed under the same custody policy.

Validate deployment data

Query the hosted relayer's /api/v1/config and /api/v1/ready, then compare the returned program ID and versions with Deployments. Do not assume Token-2022 compatibility or Mainnet readiness.

Read before shipping

• Privacy model
• SDK NoteStore and recovery
• Trusted setup
• Known limitations