Skip to content

testnet/docs/glossary.md: define ephemeral account, sweep, claim, reserve, and expiry_ledger for newcomers #575

Closed

Description

@phertyameen

File: testnet/docs/glossary.md

Someone arriving at the testnet deployment cold (e.g. a hackathon participant or partner integrator) needs a quick glossary of domain terms used throughout events and contract interfaces (AccountCreated, SweepCompleted, expiry_ledger, recovery_address) before the API reference makes sense. Add a short glossary scoped for testnet onboarding.

Activity

  1. ranjeet150 commented on Sep 19, 2026

    @ranjeet150

    Hello @maintainers,

    I would like to resolve this issue. Here is my proposed execution plan:

    • Implementation: Add comprehensive test coverage for testnet/docs/glossary.md: define ephemeral account, sweep, claim, reserve, and expiry_ledger for newcomers verifying edge cases and failure scenarios.
    • Testing: Ensure zero flake and 100% green pass rate across the test suite.

    Happy to pick this up today—please assign to me!

  2. abubakarsadiqumar550-web commented on Sep 23, 2026

    @abubakarsadiqumar550-web

    @abubakarsadiqumar550-web has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

    Hello Maintainer,

    I’d like to take on this issue. I’m available to start immediately and will work toward delivering a clean, production-ready PR within 1–2 hours of being assigned.

    Thank you for considering my application.

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

  3. jamestuns32-eng commented on Sep 23, 2026

    @jamestuns32-eng

    @jamestuns32-eng has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

    Hi Maintainer, I’m interested in working on this issue. I have experience with similar tasks and can begin immediately.

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

  4. akinkunmibobby-crypto commented on Sep 23, 2026

    @akinkunmibobby-crypto

    @akinkunmibobby-crypto has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

    Hello, I’m willing to take responsibility for this issue and work toward delivering a well-tested pull request when the task is completed.

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

  5. El-Khaleefa01 commented on Sep 23, 2026

    @El-Khaleefa01

    @El-Khaleefa01 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

    Dear Maintainer,
    I’d like to be assigned to this issue because I’m interested in making technical systems easier for new developers to understand. I can trace these domain terms through the existing contracts, events, and documentation, then turn them into concise and accurate definitions that help hackathon participants and integrators understand the testnet quickly.

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

  6. Superray23 commented on Sep 23, 2026

    @Superray23
    Contributor

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

    id like to work on this

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

  7. egwujiohaifesinachiperpetual-max commented on Sep 23, 2026

    @egwujiohaifesinachiperpetual-max

    @egwujiohaifesinachiperpetual-max has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

    please assign my ETA is 6 hrs

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

  8. oldev-hub commented on Sep 23, 2026

    @oldev-hub

    @oldev-hub has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

    Hello, I’m interested in contributing to this issue and would be grateful for the chance to take it on. Thank you for considering me.

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

  9. drips-wave commented on Sep 23, 2026

    @drips-wave

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

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

  10. grantfox-oss commented on Sep 24, 2026

    @grantfox-oss

    🎉 This issue has been marked as completed on GrantFox!

    @Superray23's PR #736 was approved and merged by @phertyameen.

    🏆 @Superray23: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,108 total points). Track your full progress on GrantFox.

    👏 Great work, @Superray23! Keep contributing to bridgelet-org.

  11. drips-wave commented on Sep 24, 2026

    @drips-wave

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

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

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions