Skip to content

Harden alpha lifecycle checks across OTC and lockup flows#6

Draft
silva-fj wants to merge 3 commits into
mainfrom
feat/otc-alpha-lifecycle-safety
Draft

Harden alpha lifecycle checks across OTC and lockup flows#6
silva-fj wants to merge 3 commits into
mainfrom
feat/otc-alpha-lifecycle-safety

Conversation

@silva-fj

Copy link
Copy Markdown
Collaborator

Summary

  • Tighten alpha lifecycle validation in the OTC, alpha lockup, and lockup listings contracts.
  • Align shared chain-extension types, events, and error handling with the updated safety rules.
  • Refresh localnet and integration coverage for listing, claim, offer, trading, and subnet risk scenarios.
  • Update the deployment/runbook and package metadata used by the integration test harness.

Testing

  • Added and updated contract unit tests for the new lifecycle constraints.
  • Extended integration tests across lockup listings and OTC flows.
  • Local validation of the updated test harness and localnet scenarios was performed as part of the change set.

silva-fj added 3 commits June 19, 2026 18:01
…cycle-safety

Conflict resolutions:
- Cargo.toml (shared, otc, lockup_listings): keep the branch's fixed =1.30.0
  pin over main's =1.27.0, and update the newly tracked Cargo.lock to match.
- README.md: keep main's rewritten structure and weave in the branch's
  lifecycle-safety docs (escrow maintenance methods, beneficiary handoff,
  TAO recovery, rollout guidance, localnet test gate).
- integration-tests/package-lock.json: take main's regenerated lockfile
  (vitest 4 bumps) and reconcile the papi descriptors version via npm install.
- Drop --minWorkers=1 from test:run and the localnet runner; the flag was
  removed in vitest 4 and now fails CLI parsing.
- Fix clippy::vec_init_then_push in lockup_listings test helper, surfaced
  by the pinned 1.89 toolchain with -D warnings.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant