Skip to contentGoverned releases
The approval record behind each reviewer release: what it superseded, what it committed to, and the transaction that approved it. This is the DAO's provenance record.
Verifying a receipt?
This page explains how a release came to be approved. It is not the place to check a receipt against. The currently approved release coordinates and the registered signer are published for that purpose at /evidence/reviewer-trust on the Epoche product site, and both are confirmable against the registries on chain.
Release entries are approved version-registry records. Signer registrations are a separate registry and may name a release that is not version-approved.
Approved releases
| Release | Release ID | Supersedes | Approval transaction | Block |
|---|---|---|---|---|
| 10 | 0x25cc634e…b179e8 | 0x3a065749…f44d73 | 0x067ff793…5d3c82 | 50809152 |
What each release committed to
These commitments are what a later challenge or incident investigation compares against. A changed commitment is a different release, not an update to this one.
Release 10 0x25cc634e…b179e8
- Source commitment
0x0ad3fb9e…efb36e- CCE policy hash
0x41258bce…c9782c- Image digest
0x8e166a61…c7aa9b- Protocol compatibility
0x5e9cc392…3e53ba- Evidence hash
0xf13b1be0…9d3398- Proof image ID
0x00000000…000000
Signer registrations
Signer registration is a separate registry from release approval. A registration may name a release the version registry has not approved, so the two are recorded apart.
| Status | Signer | Release ID | Registered until | Registration transaction |
|---|---|---|---|---|
| active | 0xC282f47d…47091a | 0x25cc634e…b179e8 | 2026-10-03 03:53:17Z | 0xc3122246…ffd09d |
| historical | 0x11e0907f…8c932A | 0x7fe8e733…e3872f | 2026-09-25 00:55:37Z | 0xb31cfa59…e1865e |