Add migration fixtures for legacy storage keys and unknown future keys

[Jagadeeshftw]

Area: Upgrade compatibility · Estimated effort: 8–12 h

Problem

contracts/grainlify-core/MIGRATION.md and storage-layout tests cover known migrations, but compatibility with legacy and forward-added keys is not explicit.

Design decision required

Decide whether unknown keys are ignored, preserved, or rejected and how migrations signal unsupported versions.

Requirements

• Seed old layouts
• run each migration
• add an unknown key
• assert values, TTL, and version markers after migration.

Acceptance criteria

• Legacy fixtures migrate deterministically, unknown keys follow the documented policy, and no unrelated storage is deleted.

Out of scope

• Unrelated refactors, dependency upgrades, or behavior changes outside the stated scope.
• Closing, deleting, or weakening existing tests to make the change pass.

Verification

cargo test --manifest-path contracts/bounty_escrow/Cargo.toml -p grainlify-core migration -- --nocapture

PR requirements

• Explain the before/after behavior and include the evidence requested above.
• Add regression tests for the changed behavior and report relevant build, test, lint, and artifact results.
• Keep the PR focused and reference this issue.
• Please open the PR within 48 hours of assignment so the work remains active; ask a question in the issue if the scope needs clarification.

Good luck, and please join the contributor Telegram group if you want to discuss the work: https://t.me/+u5qmu35nZ7I0OTU1

[Yerimahjr]

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

I’d like to work on this issue. I’ll add deterministic migration fixtures covering the supported legacy storage layouts and forward-added/unknown keys, then verify each migration preserves expected values, TTLs, and version markers without deleting unrelated storage. I’ll document the chosen unknown-key policy and unsupported-version behavior, add focused regression tests for these compatibility cases, and run the specified migration tests along with the relevant build/lint checks. I’ll keep the changes scoped to migration compatibility and include the requested before/after behavior and verification evidence in the PR.

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

[tilljack60-cmd]

@tilljack60-cmd has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

i will like to work on thiss issues

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

[baedboibidex-cmyk]

@baedboibidex-cmyk has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

pls assign

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

[Inspector222]

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

I've reviewed the issue thoroughly and can start working on it right away. I am looking forward to contributing

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

[retkatmun]

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

Hi Maintainer,

I’m a smart contract and full-stack developer and would love to contribute to this issue. I’m an experienced contributor with hands-on expertise in Rust, Soroban, Cairo, and TypeScript.

I’m passionate about building secure, scalable blockchain solutions, with a strong emphasis on writing clean and maintainable code. Based on the scope of this issue, I’m confident I can deliver a complete solution within 24 hours of assignment.

I’d greatly appreciate the opportunity to contribute and help move this forward.

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

[samjay8]

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

I'd love to work on this issue.

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

[JClark011]

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

Hi maintainer Let me work on this issue
I'll definitely give you quick response

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

[Lspnjr1]

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

I’ll like to be assigned to this issue
Kindly assigned boss

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

[damilare0813]

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

I'd be glad to handle this issue. I'll keep the implementation concise, maintainable, and well-documented

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

[Jagadeeshftw]

@tilljack60-cmd — Good luck, and thank you for taking this on! You are now assigned to Add migration fixtures for legacy storage keys and unknown future keys (#1747). Your immediate focus is add migration fixtures for legacy storage keys and unknown future keys. Please read the complete issue description before starting, address every requirement and acceptance criterion in your PR, and raise a high-quality, focused implementation with the relevant tests and verification evidence. Please include the relevant test output and explain any trade-offs in the PR. Please open the PR within 48 hours of this assignment; if no PR is opened within that period, the issue may be unassigned so the work can be reassigned. You are also welcome to join our contributor Telegram group: https://t.me/+u5qmu35nZ7I0OTU1

[drips-wave]

Congratulations, @tilljack60-cmd! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

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