[HARD][ASSET LIFECYCLE] Enforce verified, monotonic pool-asset activation and retirement

[Obiajulu-gif]

Problem

Pool-asset status can change without proving issuer, distributor, contract, metadata, supply, network, and pool identity match the live Stellar deployment.

Scope

• Define allowed and terminal state transitions.
• Before activation verify network, accounts, flags, trustlines, contract/WASM, asset code, metadata, supply, and pool identity.
• Store an immutable ledger-bound activation snapshot and evidence hashes.
• Require maker-checker approval for activation, identity changes, and retirement.
• Make active identity fields immutable; use versioned replacement.
• Block retirement while positions, supply, payouts, disputes, or archives remain.
• Add optimistic versioning and audit/domain events.

Acceptance criteria

• Mismatched deployments cannot become active.
• Validation is centralized server-side.
• Active identity is immutable and evidence reproducible.
• Retirement cannot strand balances or claims.
• Concurrent transitions resolve deterministically.

Required tests

Transition table, wrong network/account/contract/metadata/supply, stale evidence, concurrent approvals, retirement blockers, and snapshot re-verification.

Non-goals

Do not automate regulated issuance or legal eligibility.

[muokwejosh-cloud]

Hi maintainer, pls assign me to work on this issue

[JONAH-6]

I have experience building secure backend systems with strong validation and audit workflows. I've reviewed the requirements and can implement a server-side asset lifecycle with verified activation, immutable identity, ledger-bound evidence snapshots, maker-checker approvals, deterministic state transitions, and safe retirement checks. I'll also add comprehensive tests covering invalid deployments, concurrent transitions, stale evidence, retirement blockers, and snapshot re-verification before submitting a well-tested PR.

[grantfox-oss]

🦊 GrantFox — @muokwejosh-cloud has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #130)
2. Your PR will be reviewed by the Chainmove maintainers

Good luck! Track your progress on GrantFox.