Migrate `wraith-names` to persistent() storage everywhere

[truthixify]

Tier: M (2-4 days) Type: refactor

Context

PR #35's registry audit moved stealth-registry to persistent storage for scalability. wraith-names still uses instance storage in places, which has the same scaling concern. Audit + migrate.

Scope

• Audit every env.storage().instance() call in wraith-names
• For each, determine: stay instance (small fixed metadata) or migrate to persistent (per-name data)
• Migration is breaking if data is already deployed; coordinate with deploy story
• Update TTL extension logic from the keeper service (Soroban TTL keeper service for wraith-names #50 in this wave) to match

Acceptance criteria

• Storage decisions documented in wraith-names/STORAGE.md
• Migration tests pass
• TTL keeper updated to extend correct storage tier
• Deploy script updated for fresh-deploy path

Files to start with

• stellar/wraith-names/src/lib.rs
• stellar/stealth-registry/src/lib.rs (persistent storage reference)

[beebozy]

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

Hi sir, could you please assign this issue to me, I am blockchain developer and I have worked accross different chains, stellar etheruem , and other ecosystem.. Kindly assign me

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

[debbieAmoni]

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

I would like to work on this issue. I have experience reviewing smart contract code, understanding storage patterns, and working with blockchain development concepts. For this task, I will audit all env.storage().instance() usages in wraith-names, determine the appropriate storage tier for each data type, and migrate per-name data to persistent storage where necessary. I will also update the TTL extension logic, add migration tests, document storage decisions in STORAGE.md, and ensure deployment scripts support the updated storage architecture. My goal is to deliver a well-tested, maintainable solution that aligns with the scalability improvements introduced in the registry audit.

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

[truthixify]

@debbieAmoni Assigned. Welcome to wave 6.

Quick expectations to make this smooth for both sides:

1. Branch from develop (not main). PRs target develop.
2. Open a draft PR within ~3 days of pickup so we can see direction early.
3. Update at least every 5 days. Silence is the only thing that costs you the assignment; if you get stuck or context changes, just say so on the PR.
4. Read the issue body's acceptance criteria carefully. Hitting those is the merge bar.

If anything is ambiguous, ask before building.

[drips-wave]

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

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

[drips-wave]

This issue has been completed by @debbieAmoni as part of the Stellar Wave Program's 6th Wave 🥳

😎 @debbieAmoni: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.