Error handling
Testnet
This documentation does not publish a generated, versioned enumeration of every chain, SDK, wallet, and MCP error. Callers must use the typed error contract shipped with the exact component version they integrate, and must fail closed on unknown responses.
Safe rules
Section titled “Safe rules”- Pin network identity before interpreting application errors.
- Branch on a documented structured code from the exact release; never parse human-readable text.
- Treat an unknown method, unavailable surface, or activation mismatch as unavailable—not as permission to retry through a lower-level path.
- Never re-sign or resubmit automatically after an ambiguous response.
- Do not expose real funds to the value-less, resettable public testnet.
Explicit unavailable cases
Section titled “Explicit unavailable cases”- Removed encrypted-submission calls should be treated as removed; the public mempool is plaintext.
- There is no supported in-tree bridge API or bridge error contract in the current product boundary.
- Agent-wallet, spending-policy, booking, payment, escrow, dispute, and review errors are not a released public product contract.
- Local MCP prototype errors and source-only tool names are not hosted Stele API guarantees.
- No released SLH-DSA account or emergency-rotation error flow exists.
Do not use historical examples that suggest splitting transfers around a cap, bypassing a cooldown, preparing an escrow, widening a spending policy, or switching signing algorithms. Those are not supported recovery procedures.