Evidence explorer

Every artifact a live run produced: transactions, Wormhole messages and their measured finality, Cleanverse answer hashes, policy changes, refusals, and balances before and after.

Canonical happy path
gen 3

One signed intent, cash on Monad and a restricted RWA on Base, both legs delivered and read back from chain state alone.

Settlement0xf5d9093f…762f58
VerifierSETTLED_FINAL 18 of 18 checks
Artifacts10 transaction, 2 message, 3 compliance, 4 refusal, 8 conservation
Sourcedocs/evidence/phase-06-dvp.json
The run recorded UNKNOWN: “conservation broken: escrow 0 → 0”. That is the runner’s own assertion, not a chain outcome — it compared a resumed run’s closing balances against a mid-flight opening snapshot. The settlement’s chain state and the independent verification below are what say what happened.
Open evidenceVerify
Compliance changed after COMMIT
gen 3

Eligible at commit time, refused at delivery time by a RuleV2 the issuer moved in between. The cash leg had already released and was not refunded; the asset leg held, and a disposition resolved it.

Settlement0xc113ad33…01a3b0
VerifierSETTLED_FINAL 18 of 18 checks
Artifacts15 transaction, 2 message, 5 compliance, 2 policy, 3 refusal, 11 conservation
Sourcedocs/evidence/phase-07-compliance-change-0xdcb9db12.json
Open evidenceVerify
Settled from a browser
gen 3

One intent composed, checked, signed, prepared, committed, released and settled from the settlement workspace. Every transaction was sent by a wallet in a page, with each next step decided from chain state rather than by a script.

Settlement0xd46775dc…3aca77
VerifierSETTLED_FINAL 18 of 18 checks
Artifacts9 transaction, 4 message, 5 conservation
Sourcedocs/evidence/phase-06-browser-dvp.json
Open evidenceVerify
The same path, first demonstrated
gen 2

The first live HELD-then-dispositioned settlement, on the generation before the canonical one. It stays verifiable against generation-2 contracts; the current generation cannot answer for it.

Settlement0x30aa1b73…ef4a17
VerifierSETTLED_FINAL 18 of 18 checks
Artifacts15 transaction, 2 message, 5 compliance, 2 policy, 3 refusal, 11 conservation
Sourcedocs/evidence/phase-07-compliance-change-0x893ca44e.json
Open evidenceVerify

Independent verifications

SettlementCanonicalVerifierChecksGeneration
0x30aa1b73…ef4a17 SETTLED SETTLED_FINAL 18/18 0x893ca44e…1a9417
0x3f9b03f4…d3d385 SETTLED SETTLED_FINAL 18/18 0xdcb9db12…eccaa6
0x940f1c15…658858 SETTLED SETTLED_FINAL 18/18 0x9303f240…dd0843
0xc113ad33…01a3b0 SETTLED SETTLED_FINAL 18/18 0xdcb9db12…eccaa6
0xd46775dc…3aca77 SETTLED SETTLED_FINAL 18/18 0xdcb9db12…eccaa6
0xf5d9093f…762f58 SETTLED SETTLED_FINAL 18/18 0xdcb9db12…eccaa6
A verification is a claim about a settlement under one deployment generation, derived from two chain RPCs, the committed manifests and the guardian set. The application database is not an input.

Deployment manifests

ManifestDeploymentsolcContracts
contracts/deployments/base-sepolia-0x893ca44e.json 0x893ca44e…1a9417 0.8.36 ConduitRWACVA, RWACVASettlementAdapter
contracts/deployments/base-sepolia-0x9303f240.json 0x9303f240…dd0843 0.8.36 ConduitRWACVA, RWACVASettlementAdapter
contracts/deployments/base-sepolia-0xdcb9db12.json 0xdcb9db12…eccaa6 0.8.36 ConduitRWACVA, RWACVASettlementAdapter
contracts/deployments/monad-testnet-0x893ca44e.json 0x893ca44e…1a9417 0.8.36 SettlementCoordinator, CashEscrow, ConduitSandboxSettlementCVA, ConduitVaultRegistrar
contracts/deployments/monad-testnet-0x9303f240.json 0x9303f240…dd0843 0.8.36 SettlementCoordinator, CashEscrow, ConduitSandboxSettlementCVA, ConduitVaultRegistrar
contracts/deployments/monad-testnet-0xdcb9db12.json 0xdcb9db12…eccaa6 0.8.36 SettlementCoordinator, CashEscrow, ConduitSandboxSettlementCVA, ConduitVaultRegistrar
Served from the repository this Worker was built from, not from object storage. Nothing on this page claims a content-addressed publication that does not exist: ASM-039 stays open, and replacing the storage later changes where these bytes live and nothing about what they mean.