You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add a versioned contract artifact manifest and binding consistency check #41
Sub Rosa already has generated TypeScript bindings and deployed artifact notes, but integrators need a reproducible way to know which WASM, contract ID, bindings, and network metadata belong together.
Scope
Add a versioned artifact manifest for local/testnet/mainnet contract builds.
Include WASM hash, generated binding version/source, network passphrase, contract ID when known, and generated timestamp/source command.
Add a CI or test script that fails when contracts/round changes without regenerating the bindings/manifest.
Document the artifact update workflow in the existing deploy or integration docs.
Acceptance criteria
A fresh checkout can run one command to regenerate the manifest and bindings.
CI/test output clearly explains stale artifact failures.
Existing pnpm contract:test, pnpm sdk:typecheck, and binding consumers still pass.
The work fits in one focused PR without changing round behavior.
@Heazzy500 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.
my applications
Hello @maintainer, I’ve reviewed the issue description and I’m confident I can work on it effectively. Please assign it to me.
Hi! I’d love to contribute to this issue. It looks interesting and I’d be happy to take it on if it’s still available.
Hello, I’ve gone through the requirements and I’m confident I can implement a proper solution that matches the acceptance criteria. Kindly assign this issue to me.
Hi Maintainer, I’d like to work on this issue. I have experience handling similar tasks and can start immediately.
Hello, I’m interested in working on this issue and would appreciate being assigned to it. Thank you.
Hi there, I carefully reviewed the issue details and I’m confident I can deliver a clean and efficient solution.
Hello Maintainer, I’d love to take ownership of this issue and submit a high-quality pull request once completed.
Hi, I’m a full-stack Web2 & Web3 developer with open-source contribution experience, and I’d be glad to work on this issue.
Hello, this issue aligns well with my skill set and I’m confident I can resolve it properly. Please assign it to me.
Hi Maintainer! I’m interested in contributing to this task and can ensure timely delivery with clean implementation.
Hello, I’ve thoroughly read the issue description and understand the expected outcome. I’d love to work on it.
Want me to clean these up into one stronger template you can reuse?
Congratulations, @Heazzy500! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.
🧑💻 @Heazzy500: 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.
Activity
JosephOladele commentedon Jun 27, 2026
@JosephOladele has applied to work on this issue as part of the Stellar Wave Program's 6th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @JosephOladele to this issue.
Heazzy500 commentedon Jun 27, 2026
@Heazzy500 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Heazzy500 to this issue.
drips-wave commentedon Jun 27, 2026
Congratulations, @Heazzy500! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.
🧑💻 @Heazzy500: 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 🌊
feat(Sub-Rosa-Issue#41): add versioned contract artifact manifest and…
test(Sub-Rosa-Issue#41): add unit tests for artifact manifest verific…
test(Sub-Rosa-Issue#41): add unit tests for artifact manifest verific…
BWM0223 commentedon Jun 27, 2026
Submitted Artifact manifest PR #52. Implementation complete and ready for review. Payment wallets: ETH 0xeaCAb48a4bfA0CED0e668c166615927115655594 | SOL C3MD2yfWYebB8FYXpq6ooqzU5GCQB1bDxbDhQf1JfiCW | BTC bc1qtmlgtvg7xgv0zry3ct90elp3y7d3ffdutk4e2f
Merge branch 'main' into fix/41-artifact-manifest-binding-check