BE-007 · No health check endpoint for the deployed contract

[devEunicee]

BE-007 · No health check endpoint for the deployed contract

Description: There is no standard way for monitoring systems to verify the contract is live and responsive.

Acceptance Criteria:

• Add a ping(env) -> u64 function that returns the current ledger timestamp
• Document as a health check endpoint
• Off-chain monitoring calls ping every 5 minutes

Priority: Low
Effort: Small
Labels: backend, devops

---

[Jonniie]

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

Hi there, I’d like to help implement this health check endpoint. I will add the lightweight ping(env) -> u64 function to the contract, enabling it to return the current ledger timestamp so monitoring systems can verify it is live and responsive. I'll also update the documentation to outline its usage for off-chain monitoring systems executing the 5-minute heartbeat checks.
Please assign this issue to me, thank you

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

[Yourbigmike]

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

I would love to tackle this issue for the current Stellar Wave. As a computer science student and full-stack developer focusing on Web3 user interfaces, I have strong familiarity with the Stellar network and building/testing Soroban smart contracts.

I understand the architecture of ephemeral accounts and how critical it is to cleanly wire verification logic like the claim_verifier to ensure secure execution paths. I can efficiently integrate the module into bridgelet-core, ensure all data keys/states match up seamlessly, and write the necessary unit tests to verify that the implementation meets acceptance criteria without introducing regressions. Ready to dive in immediately!

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

[Julianemeka]

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

please assign

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

[drips-wave]

Congratulations, @Julianemeka! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

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