Deployment status
Know which source modules are actually published and acceptance-tested.
Trust Stack targets Supra MoveVM Testnet, chain ID 6. The deployment manifest—not a feature page or source directory—is authoritative for live package identity.
Published operations-v2 package
Package address:
0x471c6d0fdee3770657e35feaf234491ab474e54929e64ae73e55254b172a6375The recorded operations-v2 deployment includes the standard-asset modules present in that release, module bytecode/ABI readback, and real acceptance lifecycles for token creation controls, atomic batch distribution, Merkle claim and recovery, staking conservation/recovery, a vesting payroll schedule, and Digital Asset custody/release.
Separately gated work
| Capability | Status boundary |
|---|---|
| Dedicated payment stream | Implemented and locally verified; requires separate chain-ID-6 publication and lifecycle evidence |
| Dexlyn V1 LP lock | Separate adapter package; requires exact upstream package review and a real LP lifecycle |
| Digital Asset factory/media | Source and local verification require matching deployment/media evidence before shared enablement |
| Partner webhooks | Engine implemented; approved external destination and delivery evidence still required |
Release evidence checklist
Before presenting a module as live:
- run the pinned Move compile, tests, and instruction coverage;
- perform focused manual security review;
- publish or upgrade with a fresh testnet-only release identity;
- read exact bytecode and ABI back from chain;
- compare local and on-chain hashes;
- complete one real positive and required negative lifecycle;
- archive transaction links, object/resource reads, events, and source commit;
- update the typed SDK constants and deployment manifest in one reviewed release.
No mainnet approval
No Trust Stack module documented here is approved for mainnet. Testnet deployment evidence is not an independent audit or economic-safety guarantee.