Skip to content

docs/pause-circuit-breaker-design.md lists ContractPaused = 30 and an is_paused getter — the code uses 19/18/13 and is_paused_view #529

Closed

Description

@chonilius

Problem

The design doc's snippet declares ContractPaused = 30, // NEW and proposes a public is_paused(env) getter. Shipped code: escrow ContractPaused = 19, milestones 18, maintenance-pool 13, and the public getter is is_paused_view (is_paused is a private helper). Integrators decoding errors from this doc would map the wrong code.

Suggested fix

Update both to match the code, or point to scripts/error-codes.mjs as the source of truth.

Activity

  1. added
    documentationImprovements or additions to documentation
    Stellar WaveIssues in the Stellar wave program
    and removed
    Stellar WaveIssues in the Stellar wave program
    on Oct 13, 2026
  2. JoshdfG commented on Oct 19, 2026

    @JoshdfG
    Contributor

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

    Can I work in this?

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

  3. dee-john commented on Oct 19, 2026

    @dee-john

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

    i’m very conversant in solving problems like this, let me work on it

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

  4. drips-wave commented on Oct 19, 2026

    @drips-wave

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

    🧑‍💻 @JoshdfG: 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. grantfox-oss commented on Oct 21, 2026

    @grantfox-oss

    🎉 This issue has been marked as completed on GrantFox!

    @JoshdfG's PR #758 was approved and merged by @chonilius.

    🏆 @JoshdfG: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (503 total points). Track your full progress on GrantFox.

    👏 Great work, @JoshdfG! Keep contributing to MergeFi.

  6. drips-wave commented on Oct 21, 2026

    @drips-wave

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

    😎 @JoshdfG: 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

Stellar WaveIssues in the Stellar wave programdocumentationImprovements or additions to documentationgood first issueGood for newcomers

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions