Reject stale authorization nonces on admin actions

[mikewheeleer]

Summary

Signed administrative operations can be replayed if nonce consumption is not atomic and scoped.

Why this matters

This closes a correctness, security, or operability gap in the Liquifact Soroban contracts and makes the behavior explicit under authorization, replay, and storage failure.

Requirements

• Repository scope: Liquifact/Liquifact-contracts only.
• Persist a monotonic admin nonce; consume it with the state change; return a typed stale-nonce error without leaking signatures.
• Preserve storage compatibility, append-only error semantics, authorization boundaries, and event behavior unless this issue explicitly changes them.
• Add focused unit and integration coverage for the new behavior.

Technical guidance

• Follow the existing DataKey, storage TTL, auth, event, and typed-error conventions in the repository.
• Keep state changes atomic, bounded, and safe under retries or concurrent invocations.
• Document non-obvious security assumptions and include test evidence in the PR.

Edge cases — each must have a test

• next nonce
• old nonce
• future nonce
• two same-nonce calls
• nonce near maximum

Acceptance criteria

• Every requirement and edge case above is implemented and tested
• Unit and integration tests cover success, failure, authorization, replay, and boundary paths
• Existing tests pass with no regressions
• Errors are structured, stable, and do not leak internal details
• cargo fmt --all -- --check, cargo clippy --all-targets -- -D warnings, and cargo test passes locally
• Code follows existing conventions with no duplication or dead code
• Documentation or concise Rustdoc comments explain non-obvious decisions
• PR description explains the approach, includes test evidence and security notes, and references Closes #

Out of scope

• multi-signature policy design

[adeboladee]

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

Kindly assign this task to me maintainer,i would fix this,bug and conflict free

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

[drips-wave]

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

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

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Third Campaign campaign!

@adeboladee's PR #1246 was approved and merged by @mikewheeleer.

🏆 @adeboladee: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (831 total points). Track your full progress on GrantFox.

👏 Great work, @adeboladee! Keep contributing to Liquifact.

[drips-wave]

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

😎 @adeboladee: You earned 100 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.