Ascend

Home Transactions Identity About

Preprod

Preprod
Mainnet

Disclosures

Stablecoins. The stablecoins here are test stand-ins. tUSDM and tUSDCx are minted by this repo's operator. On mainnet these are replaced by the verified USDM and USDCx policies.
KERI infrastructure. KERI infrastructure is self-hosted. It runs one KERIA agent with three separate client key stores, alongside the standard demo witness pool. The trader AID aliases still read "ascend-investor-N" because they were named before the rails were.
Settlement timing. Settlement timing (settle_after) is measured against the timestamp on the attested price update, not against an on-chain clock. Production adds transaction validity bounds to cap staleness, following the Pyth docs.
Metadata and CIP status. Metadata label 7368, which carries Ascend app data, is not registered. CIP-0170 is still at Proposed status. All shapes are pinned to the text in the CIPs repo.
Scope of this evidence. This is testnet TRL5 evidence, not the audited mainnet build. The mainnet deployment goes through a third-party audit as set out in the funded plan.
Pyth updates. Price updates are fixture-signed on testnet. The wire format, feed ids and exponents are real, and the payload is signed with ed25519 using this repo's declared fixture publisher key. Only the prices themselves are synthetic.
On mainnet, verification switches to the live Pyth withdraw scripts, which Pyth has already deployed, and to live Pyth Pro updates. Nothing downstream changes shape.

The on-chain parser here handles a fixed single-feed layout of price and exponent. Production uses the parser from the official pyth-lazer-cardano library.

MIT · on-chain layer + tooling