Prism turns opaque Soroban errors into plain English, replays historical transactions against reconstructed ledger state, and lets you step through contract execution with full time-travel debugging. It handles everything from decodingDocumentation Index
Fetch the complete documentation index at: https://prism-ddf93e61.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Error(Contract, #3) into the actual enum name defined in the contract, to showing you exactly which host function call consumed the last byte of your CPU budget.
Why Prism Exists
Soroban errors are notoriously opaque.HostError(Budget, LimitExceeded) tells you the budget was exceeded but not which call was expensive. Error(Contract, #3) tells you the contract returned error number three but not what three means.
Today, developers debug these errors by grepping through Stellar Core source code, adding print statements, or asking on Discord. Prism is the missing diagnostic layer designed to give you the answer in seconds, not hours.
The 3-Tier Model
Prism is organized into three tiers of depth, each building on the one before it.Tier 1: Decode
Instant error classification and contract-specific resolution.
Tier 2: Trace
Historical state reconstruction and hierarchical execution timelines.
Tier 3: Time-Travel
Interactive breakpoints, stepping, and “what-if” re-simulation.
Supported Networks
| Network | Decode (Tier 1) | Replay (Tier 2–3) | Source |
|---|---|---|---|
| Mainnet | Yes | Yes | Soroban RPC + History Archives |
| Testnet | Yes | Yes | Soroban RPC + History Archives |
| Futurenet | Yes | Limited | Soroban RPC (archive coverage varies) |
| Custom | Yes | Yes | User-configured RPC endpoint + archives |