Issue: Add Escrow Version and Upgrade Tracking

[OlufunbiIK]

Complexity: Hard
Labels: contracts, soroban, storage, drips-wave, stellar-wave
Description: Track the contract version on-chain so deployed instances can be identified and upgrade history can be audited.
Requirements:

Store version: String (e.g. "1.0.0") in contract storage on initialize
get_version(env) — public, returns current version string
upgrade_version(env, new_version) — admin only
Emit ContractUpgraded event with old and new version
Version must follow semver format (validated on set)

Files to Update:
contracts/split-escrow/src/lib.rs
contracts/split-escrow/src/events.rs
Acceptance Criteria:
[ ] Version stored and returned correctly
[ ] Admin can update version
[ ] Non-admin update attempt fails
[ ] ContractUpgraded event emitted
[ ] Unit tests included
Estimated Time: 3-4 hours

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[Yusufolosun]

@Yusufolosun has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Good day Maintainer
I would love to take on this issue, I've reviewed the issue description and I can implement a maintainable solution fast.
I'm active and i respond and react to feedback fast

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

[Obiajulu-gif]

@Obiajulu-gif has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Can I work on this issue

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

[Chinonso-Peter]

@Chinonso-Peter has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

I would love to work on this

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

[Nanfe01]

@Nanfe01 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hello Maintainer, I'll like to work on this issue

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

[fredericklamar342-prog]

@fredericklamar342-prog has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hello,

I’m applying to implement the Escrow Version and Upgrade Tracking feature.

I work with smart contract systems where correctness, upgrade safety, and on-chain traceability are critical. For this task, I’ll implement a clean and secure versioning layer that aligns with Soroban storage patterns and upgrade best practices.

My approach:

Store version in contract instance storage at initialization using a deterministic key

Implement get_version(env) as a lightweight read with no side effects

Restrict upgrade_version(env, new_version) strictly to admin (using existing auth patterns)

Validate semantic versioning (major.minor.patch) before storage to prevent invalid states

Emit a ContractUpgraded event with both old and new versions for auditability

Ensure storage writes are minimal and efficient

Security & reliability focus:

Prevent unauthorized upgrades via strict access control

Ensure version immutability unless explicitly upgraded

Avoid malformed version strings entering contract state

Keep event emission consistent for off-chain indexers

Testing:

Unit tests for initialization, version retrieval, successful upgrade

Negative tests for non-admin access and invalid semver input

Event emission verification

I can deliver this within the expected timeframe with clean, production-ready code that integrates seamlessly into the existing contract.

Happy to start immediately.

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

[drips-wave]

Congratulations, @fredericklamar342-prog! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on March 30, 2026.

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