Vigil
State lifecycle manager for Soroban — TTL monitoring, auto-bump, and archival recovery.
Vigil watches every piece of state in your Soroban contracts, warns you before anything expires, automatically bumps the entries that matter, and recovers state that has already been archived.
0.
Features
- Continuous TTL monitoring: Scans all storage entries (Instance, Persistent, Temporary) every ledger close.
- Multi-channel alerting: Configurable thresholds with alerts via webhook, email, and dashboard.
- Auto-bump engine: Define policies that keep critical state alive automatically based on budget and priority.
- Batch transaction optimization: Aggregates multiple bump operations into minimal transactions to save fees.
- Archival recovery: Locates archived state from snapshots and constructs restoration transactions.
0.
Architecture
Vigil is organized into five internal layers:
- Scanner: Discovers keys and polls TTLs to build a state inventory.
- Alert Engine: Evaluates thresholds and fires warnings across channels.
- Policy Evaluator: Matches entries against bump policies and fee budgets.
- Bump Executor: Batches
extendTTLoperations, signs, and submits transactions. - Recovery Service: Locates archived state and restores it with a bump policy.
0.
Storage Types Handling
| Type | Archival Behavior | Vigil Handling | | :--- | :--- | :--- | | Instance | Archived when TTL expires | Monitored, auto-bumped, recoverable | | Persistent | Archived when TTL expires | Monitored, auto-bumped, recoverable | | Temporary | Permanently deleted | Monitored and alerted only (not recoverable) |
0.
Security Model
- Scoped signing keys: Uses dedicated bump keys separate from deployment keys.
- Non-custodial mode: Vigil can call user-provided signing webhooks to avoid holding secret keys.
- Hard fee caps: Policies enforce strict budgets to prevent account drainage.
On This Page
Learn more about the Stellar Ecosystem at stellar.org