Environment checklist
| Requirement | Purpose |
|---|---|
| Arcane Solana SDK access | Build and submit private payment operations from your backend |
| Solana RPC endpoint | Read deposit balances and confirm transactions |
| Arcane API endpoint | Access indexer and relayer APIs |
| Light RPC endpoint | Support compressed account state where required |
| Circuit artifacts | Generate proofs for private transactions |
| Backend database | Persist wallet rows, scan progress, UTXOs, encrypted outputs, and operation history |
Backend environment
Keep configuration server-side.https://yona.cash/api. The default circuit path is /transaction2.
Test sequence
- Connect an external Solana wallet.
- Create or restore the backend wallet row.
- Initialize scan state.
- Display a stealth deposit address.
- Send a small test amount to that address.
- Check the public balance through Solana RPC.
- Shield the funds with
depositWithRelayer. - Scan private state with
getMyUtxos. - Submit a small private spend or withdrawal.
- Confirm status history and reconciliation data.
Go-live gate
Move to production only after:- The first private transaction succeeds in testnet or sandbox.
- Wallet rows, scan progress, decoded UTXOs, encrypted outputs, and operation history persist correctly.
- Secrets are stored in KMS, HSM, or an equivalent managed signing layer.
- Retry behavior is idempotent.
- Support can find product records by transaction signature.