Publish Testnet Contract Registry (IDs + Config Snapshot)

[Cedarich]

Complexity Score: 100

Description

Create a single source of truth for Testnet contract addresses and init configuration used by the app.

Requirements

• Record contract ID(s), deployer address, wasm hash, and init args.
• Include a timestamp and git commit SHA for the deployed build.
• Ensure registry format is machine-readable (JSON or env-style mapping) and easy for contributors to update.

---

[JohnOluB]

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

I’ll start by auditing the current deployment flow to collect contract IDs, deployer address, wasm hash, and init arguments, then define a single machine readable registry format in JSON or env style with timestamp and git commit SHA to ensure traceability and consistency for Testnet deployments.

I have experience working with blockchain deployment workflows and will ensure this registry is easy to maintain, accurate, and usable by all contributors on Pulsefy Soter.

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

[drips-wave]

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

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

[neyij]

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

hi, i would like to work on this.

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

[chinweobtagaz]

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

can i handle this issue ???

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

[drips-wave]

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

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