Skip to content

Concepts: state archival and TTL management #632

Closed

Description

@codebestia

Branch: Open your PR against dev. PRs targeting main are closed automatically.

Description:
Write contracts/docs/concepts-state-archival.md: how each contract uses Soroban's instance, persistent and temporary storage, and how it extends TTLs so live state is never archived. A treasury whose member list or open proposals are archived is unusable until restored.

Acceptance criteria:

  • A per-contract table: every storage key, its durability class, and where its TTL is extended
  • Documents the TTL thresholds and extension amounts used, and the reasoning behind them
  • Identifies any keys that are written but never extended, and records them as risks
  • Documents how an operator restores archived state, with the stellar CLI command

Activity

  1. Andreas2410 commented on Oct 19, 2026

    @Andreas2410

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

    I'd like to work on this issue

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

  2. Netty-kun commented on Oct 19, 2026

    @Netty-kun

    @Netty-kun has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hello! I’d be happy to contribute to this task.

    I’m comfortable picking up unfamiliar codebases, tracing existing behavior, and making focused changes without disrupting other functionality. I’ll take ownership of the implementation from understanding the requirements through testing and final verification.

    I’d appreciate the opportunity to work on it.

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

  3. Dannyorji commented on Oct 20, 2026

    @Dannyorji
    Contributor

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

    Hi Maintainer
    I will like to work on this.

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

  4. drips-wave commented on Oct 20, 2026

    @drips-wave

    Congratulations, @Dannyorji! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.

    🧑‍💻 @Dannyorji: 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 🌊

  5. github-actions commented on Oct 20, 2026

    @github-actions

    Closed by #646, merged into dev.

  6. drips-wave commented on Oct 20, 2026

    @drips-wave

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

    😎 @Dannyorji: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions