Implement Soroban Contract State Snapshot with Point-in-Time Recovery Capability

[temma02]

Description

There is no mechanism to snapshot Soroban contract state at a specific ledger for point-in-time recovery. Implement a state snapshot service that captures all persistent storage entries at a given ledger and supports restoring them to a Soroban sandbox for debugging.

Requirements and Context

• Snapshot: enumerate all ContractData ledger entries for a contract at a given ledger
• Store snapshots in Supabase with ledger number, contract ID, and compressed state blob
• Restore: load snapshot into a Soroban simulation context for offline replay
• Snapshot size limit: 10MB per contract per snapshot

Suggested Execution

Branch: feat/soroban-contract-state-snapshot-recovery

Implement Changes

• Create contract-state-snapshot.ts in packages/stellar/src/
• Use Horizon /ledger/{sequence}/effects to enumerate storage changes
• Compress and store snapshots in Supabase Storage with metadata in DB
• Add tests for snapshot creation, compression, and offline restore

Test and Commit

Run pnpm test --filter=stellar -- contract-state-snapshot and confirm snapshot and restore roundtrip tests pass.

Example Commit Message

feat(soroban): add contract state snapshot service with point-in-time recovery

Co-authored-by: <your-name>

Guidelines

• Branch off main, keep PRs focused on one issue
• All new code must include unit or integration tests
• Ensure pnpm lint and pnpm typecheck pass before review
• Link this issue in your PR description
• Request review from at least one maintainer before merging

[Adesam007-pr3dator]

@Adesam007-pr3dator has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi, I would love to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Adesam007-pr3dator to this issue.

[observerr411]

@observerr411 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I would like to take on this task

ℹ️ Repo Maintainers: To accept this application, review their application or assign @observerr411 to this issue.

[drips-wave]

Congratulations, @observerr411! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @observerr411: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @observerr411 as part of the Stellar Wave Program's 6th Wave 🥳

😎 @observerr411: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.