Asset · USTB
Superstate Short Duration U.S. Government Securities Fund
LIVETouchstone reads this fund's public Superstate disclosures every day, compiles the approved controls over the captured bytes, and publishes a signed report to X Layer mainnet and testnet. Both of its policies read CONFIRMED, and a consumer contract on mainnet acts on that answer.
- Asset key
eip155:1:0x43415eb6ff9db7e26a15b704e7a3edce97d31c4e- Registry key
0x82287f6355a79c8cf00b3c52090128ae7f13b61c65c95ae1c319910377054cc8- Networks
- X Layer mainnet (chain id 196) and X Layer testnet (chain id 1952)
- Publisher key
ed25519:394ee022b83de4783cd49f60cc4842b48d108f6a339b73272739490cb9a581fd
Current policy verdicts
A policy is a versioned subset of the approved controls, published under its own registry key so a consumer can read the one question it cares about. Both USTB policies were first confirmed on 2026-08-19 and are attested on registry v2 as EIP-712 reports a relayer submits.
disclosure-freshness:1
CONFIRMEDDisclosure freshness
Is the issuer still publishing the disclosures it says it publishes, on the cadence it declares? A listing monitor needs that answer, and should not be told nothing merely because a valuation has not settled yet.
Read this verdict live →nav-settlement:1
CONFIRMEDNAV settlement
Has the net asset value this asset would be lent against actually settled? It asks for more than freshness — a NAV row held unchanged by a later capture — and it refuses when freshness alone would pass.
Read this verdict live →Reports expire at the end of the UTC day and re-publish at the daily window. The terminal reads the registry at the block you ask, so what it shows is the chain's answer, not this page's memory of it.
Refused, then confirmed
A NAV value was provisional. Touchstone refused it. The same value later survived the required evidence interval, became confirmed, and changed the behaviour of a consumer contract — without any control being weakened in between.
2026-08-18
Refused
The NAV row was present and fresh, but it had not settled. The settlement policy asks for a NAV held unchanged by a capture at least 24 hours older and at least 2 business days settled, so it declined to answer from a figure the issuer could still restate.
The interval
Nothing was relaxed
No control was edited and no threshold lowered while the refusal stood. The approved USTB control set remained 5 controls under approval ledger 0x4f2c7dd5ea0cd09c3b0e9d51445873c65b882a1b3b3265c15979b598dab91dd1, signed by 0x537873b087654395CB0A487B50d0bFBe15fA16Bc. The run waited for evidence instead.
2026-08-19
Confirmed
The same NAV — 11.18316100 as of 2026-08-18 — survived the interval, and both policies published CONFIRMED: mainnet at block 68512680, testnet at block 38698679.
Consumer effect
A contract changed answer
The mainnet gate at
0xAac48DC261B04737FDCB101D5049395121034a83
answered (true, "allowed") for the disclosure-freshness key it pins
from 2026-08-19 — verdicts expire at end of day UTC and
renew at the daily window — and the action it guards executed on chain. The gate is immutable: its code did not change, its
input did.
Publication history
Sequences are per registry key and per chain, and they only move forward. The asset report publishes to registry v1; each policy verdict publishes to registry v2 as a relayer-submitted EIP-712 attestation.
X Layer testnet
| Seq | Epoch | Key | Registry | State | Bundle |
|---|---|---|---|---|---|
| 1 | ustb-2026-08-19 |
nav-settlement:1 | v2 | CONFIRMED LATEST | bundle file lost to a same-name overwrite; signed report retained in the transparency log |
| 1 | ustb-2026-08-19 |
disclosure-freshness:1 | v2 | CONFIRMED LATEST | bundle file lost to a same-name overwrite; signed report retained in the transparency log |
| 4 | ustb-2026-08-19 |
asset key | v1 | CONFIRMED LATEST | Download |
| 3 | ustb-2026-08-17 |
asset key | v1 | UNVERIFIABLE CORRECTS 1 | Download |
| 2 | ustb-2026-08-18 |
asset key | v1 | UNVERIFIABLE | Download |
| 1 | ustb-2026-08-17 |
asset key | v1 | UNVERIFIABLE | Downloadfirst publication · transaction · block 38526525 |
Sequence 3 corrects sequence 1 and carries sequence 1's epoch, so for a time the latest testnet publication pointed at an epoch older than sequence 2's. That is the correction model working as designed: a correction supersedes the sequence it names without rewriting it, and a reader follows the sequence, not the calendar.
X Layer mainnet
| Seq | Epoch | Key | Registry | State | Bundle |
|---|---|---|---|---|---|
| 3 | ustb-2026-08-21 |
nav-settlement:1 | v2 | CONFIRMED LATEST | Download |
| 3 | ustb-2026-08-21 |
disclosure-freshness:1 | v2 | CONFIRMED LATEST | Download |
| 5 | ustb-2026-08-21 |
asset key | v1 | CONFIRMED LATEST | Download |
| 2 | ustb-2026-08-20 |
nav-settlement:1 | v2 | CONFIRMED | Download |
| 2 | ustb-2026-08-20 |
disclosure-freshness:1 | v2 | CONFIRMED | Download |
| 4 | ustb-2026-08-20 |
asset key | v1 | CONFIRMED | Download |
| 1 | ustb-2026-08-19 |
nav-settlement:1 | v2 | CONFIRMED | Download |
| 1 | ustb-2026-08-19 |
disclosure-freshness:1 | v2 | CONFIRMED | Download |
| 3 | ustb-2026-08-19 |
asset key | v1 | CONFIRMED | Download |
| 2 | ustb-2026-08-18 |
asset key | v1 | UNVERIFIABLE CORRECTS 1 | Download |
| 1 | ustb-2026-08-18 |
asset key | v1 | UNVERIFIABLE | Download |
first mainnet publication: 0xfa4b7992bee12819017ca16a0d338d629e86b0bf2d3487f6dd07abfe6bef0b85 · block 68292878
Evidence authorities
3 issuer-published JSON endpoints stand behind every USTB verdict. Touchstone reads public Superstate disclosures; it is not a party to them.
| Source | What a control may quote from it |
|---|---|
superstate-ustb-nav-daily |
The daily NAV row: the per-share value and the date it is stated as of. |
superstate-ustb-yield |
The published yield row and the date it is stated as of. |
superstate-ustb-holdings |
The holdings disclosure and the date it is stated as of. |
Every fetch is stored as a digest-addressed capture. A control quotes a byte span from a named capture rather than a value someone retyped, the report carries the evidence root over those captures, and a reader can recompute both offline from the signed bundle. How sources are audited →
Contracts
Several addresses exist on both chains as different contracts, so the chain id is the discriminator. These are the registries USTB publishes to.
| Contract | Network | Address | Deployed at block |
|---|---|---|---|
| Registry v2EIP-712 attested reports | X Layer mainnet · 196 | 0x0dAb4A5B7dd24434Ab6564734E26d3d76985352C | 68389940 |
| Registry v1publisher-authenticated commitments | X Layer mainnet · 196 | 0xc9d58e4496bF061C3177301Ff02518eBB70AD30d | 68291416 |
| Registry v2EIP-712 attested reports | X Layer testnet · 1952 | 0xBaE680e671e0451b95c9b09eD15F70C3E1EA7720 | 38699818 |
| Registry v1publisher-authenticated commitments | X Layer testnet · 1952 | 0x0dAb4A5B7dd24434Ab6564734E26d3d76985352C | 38489602 |
Downloads
- Mainnet · nav-settlement:1 · latesteip155-196-ustb-2026-08-21-3-policy-nav-settlement-1.json
- Mainnet · disclosure-freshness:1 · latesteip155-196-ustb-2026-08-21-3-policy-disclosure-freshness-1.json
- Mainnet · asset key · latesteip155-196-ustb-2026-08-21-5.json
- Mainnet · nav-settlement:1ustb-2026-08-19-1-policy-nav-settlement-1.json
- Mainnet · disclosure-freshness:1ustb-2026-08-19-1-policy-disclosure-freshness-1.json
- Mainnet · asset keyustb-2026-08-19-3.json
- Testnet · asset keyustb-2026-08-19-4.json
23 signed bundles are published in total, including the superseded sequences above. The dossier indexes every one, and /verify shows how to check a bundle without trusting this site.
Read it live
Every value on this page is a claim about a registry. The terminal reads that registry in your browser, names the block it read, and lets you simulate and execute the guarded action the gate protects.