Recovery key with cooldown

[Miracle656]

Background

A designated recovery key that can rotate signers after a 7-day timelock prevents instant takeover.

What to build

Extend the contract with request_recovery (starts cooldown) and finalize_recovery (after ledger > unlock_at).

Key files

• contracts/wallet/src/recovery.rs (new)

Acceptance criteria

• Cooldown enforced
• Cancellation by current signer works
• Tests cover happy/cancel paths

Drips Wave · Complexity: Advanced · 200 points

[emickwrld]

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

Hello Maintainer, I'm excited about this issue and would like to be assigned. I'll document my approach in the PR description so the team can follow my reasoning and suggest improvements early.

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

[ezedike-evan]

@ezedike-evan 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 issue. I will create recovery.rs and implement request_recovery to record the recovery key, the new intended signer, and the unlock ledger timestamp calculated as the current ledger plus the 7-day equivalent in ledgers, and finalize_recovery to verify the cooldown has elapsed before rotating the signer and rejecting the call early if the unlock ledger has not been reached. I will also implement cancellation logic that allows the current active signer to abort a pending recovery request before it finalizes, removing the pending state cleanly so the recovery key cannot proceed after cancellation. I will write tests covering the happy path end to end, a premature finalize attempt that should be rejected, and the cancellation flow to make sure all three acceptance criteria are verifiable with cargo test before submitting. Can I be assigned?

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

[drips-wave]

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

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