Skip to content

Contract error and panic reference #580

Closed

Description

@codebestia

Write contracts/docs/contracts-errors.md: every failure condition across the three contracts — what triggers it, what the caller observes, and how a client should present it.

Acceptance criteria:

  • Every panic/error path documented per contract function, grouped by function
  • Distinguishes authorization failures, validation failures and state-machine violations (voting twice, approving after expiry, executing an unfinalised proposal)
  • Documents what a failed invocation looks like from the frontend, so lib/soroban.ts callers can map it to a message
  • Cross-links the frontend error-handling doc

Activity

  1. Zuno2026 commented on Aug 27, 2026

    @Zuno2026

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

    I would love to solve the issue in this field because I’m an experienced Troubleshooting Engineer

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

  2. 0xDeon commented on Aug 30, 2026

    @0xDeon
    Contributor

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

    Hello team.

    I’m Deon (0xDeon), a software engineer with a strong background in building scalable systems and contributing to open-source projects. I’ve taken some time to go through the repository and understand the current implementation, and I’m clear on the issue, its context, and the expected outcome.

    I’d love to work on this and take ownership of the fix. I’m confident I can cleanly resolve it while keeping everything aligned with the existing codebase and ensuring all criteria are met. Would appreciate being assigned to this issue.

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

  3. drips-wave commented on Aug 30, 2026

    @drips-wave

    Congratulations, @0xDeon! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

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

  4. github-actions commented on Aug 31, 2026

    @github-actions

    Closed by #602, merged into dev.

  5. drips-wave commented on Aug 31, 2026

    @drips-wave

    This issue has been completed by @0xDeon as part of the Stellar Wave Program's 8th Wave 🥳

    😎 @0xDeon: 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.

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 programcontractsdocumentationImprovements or additions to documentation

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions