Protocol resilience
CookLab separates canonical on-chain truth from off-chain availability. RPC providers, indexers, the Telegram interface, and the discovery application can be replaced or recovered without changing token supply, market reserves, vesting state, fee entitlements, or ownership recorded by the Solana program.
Resilience means the system can lose an interface or index without losing canonical market truth. Recovery procedures start from finalized chain state and rebuild every derived view.
Canonical versus derived
Token balances, reserves, vesting, and lifecycle status live on Solana. Search results, rankings, charts, alerts, and cached token metadata are derived services that may temporarily lag and can be reconstructed.
- Finalized signature cursor
- Idempotent event processing
- Oldest-first replay
- Health indicators for data freshness
Operational signals
Operators should monitor RPC latency, finalization delay, indexer cursor age, Telegram polling health, failed transaction classes, wallet withdrawal failures, storage growth, and unexpected program events.
- Alert on stale finalized data
- Separate user errors from infrastructure errors
- Back up encrypted operational state
- Test restoration instead of assuming it works
Continuity principle
An outage must degrade convenience before it threatens correctness. When canonical state cannot be read with confidence, value-moving interfaces should fail closed and recover through reconciliation rather than optimistic assumptions.
- No trading on stale authoritative state
- No fabricated success responses
- Multiple RPC providers where appropriate
- Post-recovery balance reconciliation