Skip to content

Unify pause function naming across contracts #550

Closed

Description

@DeFiVC

Severity: low
Labels: enhancement, rust, Stellar Wave

What

Rename emergency_pause in credential-nft and progress-tracker to pause to match learn-token's naming, or rename learn-token's pause to emergency_pause for consistency.

Why

Learn-token uses pause/unpause while credential-nft and progress-tracker use emergency_pause/unpause. This inconsistency confuses integrators.

Scope

  • Choose one naming convention (recommend pause/unpause as it is shorter)
  • Rename in credential-nft and progress-tracker
  • Update all tests that call the renamed function
  • Update documentation (README API tables, integration guide)
  • Update scripts that invoke the function

Out of scope

Changing the pause logic itself.

Acceptance criteria

  • All three contracts use the same function name for pause/unpause
  • All tests pass
  • Documentation updated

Technical context

contracts/credential-nft/src/lib.rs and contracts/progress-tracker/src/lib.rs contain emergency_pause. contracts/learn-token/src/lib.rs contains pause.

Activity

  1. added
    enhancementNew feature or request
    rustRust language
    Stellar WaveIssues in the Stellar wave program
    lowCosmetic, minor improvement, code quality, documentation
    and removed
    Stellar WaveIssues in the Stellar wave program
    on Oct 14, 2026
  2. joannaomotunde commented on Oct 20, 2026

    @joannaomotunde

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

    Please Maintainer, assign this ssue to me. Thank you so much

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

  3. codefather2026 commented on Oct 20, 2026

    @codefather2026

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

    Hi maintainer, i will like to solve this issue

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

  4. Emoji-dot commented on Oct 20, 2026

    @Emoji-dot

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

    I would like to work on this issue

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

  5. thisismizz commented on Oct 20, 2026

    @thisismizz

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

    Hi maintainer, I can fix this issue. Please assign

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

  6. TheHalalHunter commented on Oct 20, 2026

    @TheHalalHunter
    Contributor

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

    Hi maintainer
    I’d love to help out with this issue. I’ve checked the current codebase/documentation and know exactly what needs to be updated to make this clearer. I will ensure everything aligns perfectly with your existing contribution guidelines.

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

  7. drips-wave commented on Oct 20, 2026

    @drips-wave

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

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

  8. grantfox-oss commented on Oct 21, 2026

    @grantfox-oss

    🎉 This issue has been marked as completed on GrantFox!

    @TheHalalHunter's PR #677 was approved and merged by @DeFiVC.

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

    👏 Great work, @TheHalalHunter! Keep contributing to ChainLearnOfficial.

  9. drips-wave commented on Oct 21, 2026

    @drips-wave

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

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

Labels

Stellar WaveIssues in the Stellar wave programenhancementNew feature or requestlowCosmetic, minor improvement, code quality, documentationrustRust language

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions