soroban-storage-ttl-lifecycle
Soroban ledger state rent and TTL extension register: live state tracking, bump thresholds, rent fee reserves, and archive boundaries.
Try your first task
A source-grounded starter task has not been verified for this skill yet.
SKILL.md
name: soroban-storage-ttl-lifecycledescription: 'Soroban ledger state rent and TTL extension register: live state tracking, bump thresholds, rent fee reserves, and archive boundaries.'category: engineeringrisk: safesource: selfsource_type: selfdate_added: "2026-10-01"author: Ranjeet2063tags: [soroban, storage, ttl, state-archival, stellar, gas, rust]tools: []source_repo: Ranjeet2063/agentic-awesome-skillsSoroban Storage TTL & Rent Lifecycle
What it is: Tracks storage TTL exhaustion boundaries, automated ledger rent extensions, and archival prevention policies for production Soroban contracts.
Overview
Provides a standardized, auditable framework and data model for Soroban Storage TTL & Rent Lifecycle operations across distributed engineering and decentralized application systems.
When to Use This Skill
- When formalizing architectural contracts, security invariants, or operational limits for Soroban Storage TTL & Rent Lifecycle.
- When cross-functional review is required between protocol developers, smart contract auditors, and AI engineering agents.
- When generating reproducible CSV, SQL DDL, JSON Schema, and Notion property registers for tracking compliance.
How It Works
- Define the parameters, thresholds, and identity bindings required for the target operational register.
- Select appropriate boundary enforcement values from validated enum select sets.
- Export standardized artifacts (CSV table, SQL DDL, JSON Schema) to integrate into validation CI pipelines.
Verification procedure
Bind each record to network, current ledger, contract/code identity, storage type and exact ledger entry key. TTL is measured in ledgers, not wall-clock seconds; do not assume fixed ledger cadence. Persistent and instance entries archive on expiry, whereas temporary entries are removed and cannot be restored. Track instance/code and persistent-key lifetimes as the actual protocol/API requires; an Auto-Bump field does not schedule anything. Inspect current network maximum TTL and simulation/resource fees before any extension. Test threshold equality, expired/missing entries, restore requirements and insufficient fee budget on a disposable fixture, then verify post-operation live-until ledger. A monitoring label alone does not prove an extension succeeded.
Field Reference
| # | Field Name | Type | SQL Type | JSON Schema Type | Notion Property Type | Example Value |
|---|---|---|---|---|---|---|
| 1 | TTL Monitoring ID | id | VARCHAR(64) PRIMARY KEY | string | Text | TTL-001 |
| 2 | Contract Address | text | VARCHAR(56) | string | Text | CVLT... |
| 3 | Storage Tier Lifetime | select | VARCHAR(32) | string | Select | Persistent |
| 4 | Key Identifier Name | text | VARCHAR(64) | string | Text | UserShareBalance |
| 5 | Current TTL Remaining Ledgers | number | INTEGER | number | Number | 125000 |
| 6 | Minimum Threshold Ledgers | number | INTEGER | number | Number | 50000 |
| 7 | Auto-Bump Amount Ledgers | number | INTEGER | number | Number | 250000 |
| 8 | Rent Fee Budget XLM | currency | NUMERIC(14,7) | number | Number | 10.0000000 |
| 9 | Archival Risk Status | select | VARCHAR(32) | string | Select | Safe Extended |
| 10 | Last Extended Ledger | number | BIGINT | number | Number | 54820100 |
| 11 | Monitoring Audit Date | date | DATE | string, format: date | Date | 2026-10-01 |
Select Options
Storage Tier Lifetime
Instance | Persistent | Temporary
Archival Risk Status
Safe Extended | Threshold Reached | Critical Expiring | Archived
Relations
Audit Reference-> links to the formal review documentation or test repository.Target Architecture-> links to the deployed contract or autonomous agent runtime component.
Examples
Prompt
How do I configure and track Soroban Storage TTL & Rent Lifecycle for our production environment?
Recommended Next Step
Generate the unified field schema, SQL DDL migration, and JSON validation schema to register into your system catalog.
Workflow: Define criteria -> Run automated verification -> Record baseline -> Monitor invariants.
Best Practices
- Enforce strict typing on numerical bounds and currency amounts; avoid unstructured free-text fields for critical states.
- Re-run validation test suites on every state-altering commit or parameter change.
- Keep example data synthetic and isolated from production cryptographic keys or private endpoints.
Limitations
- Provides architectural specifications, data models, and verification schemas; does not execute direct transaction signing without authorized external tooling.
- Requires network connectivity and valid RPC credentials when querying on-chain states.
Security & Safety Notes
- All parameters declare
risk: safe. No unauthorized state modification or privileged credential access is performed. - Use synthetic dummy keys and mock addresses in test suites and local verification scripts.
Common Pitfalls
- Problem: Mismatched decimal precision between contract runtime and database register. Solution: Always verify decimals using the explicit field mapping in this reference.
- Problem: Missing authorization checks prior to state update. Solution: Cross-validate against the Security Audit register before deployment.
Related Skills
- @soroban-contract-audit - provides the security checklist and vulnerability categorization.
- @soroban-oracle-data-feed-audit - covers oracle heartbeat and stale-price handling.
- @web3-rate-limiting-circuit-breaker - provides operational guardrails and threshold breakers.
Reusable Prompt
I want to establish a verified Soroban Storage TTL & Rent Lifecycle register for our production protocol.
Guide me through the required field parameters and output the corresponding SQL DDL and JSON Schema.