Zero Indexer attestations

Independent observations of the experimental shims and hubs serving Zcash wallets. Check their enclave evidence, connection certificates and software release status.

MAINNET · EXPERIMENTAL

Registered endpoints: 2
Evidence + TLS verified: 1
Software releases matched: 0

Valid enclave evidence and a matching connection do not confirm the software release. Each check is reported separately.

ENDPOINT_OBSERVATIONS

Primary · 5 min / Canary · 1 min

Zec.rocks

shim

tee.unsafe.zec.rocks:443

Check failed

Enclave evidence: Verified
TLS certificate: Matched
Software release: Measurements differ

Canary observerSigned check failed

Observed 2026-10-15 05:46:33 UTC · expires 2026-10-15 05:49:33 UTC

The measurements differ from the configured release baseline.

Last attempt 2026-10-15 05:45:16 UTC

Build, configuration & evidence

Reviewed build: deploy-fdb613db-a606726Current match unconfirmedCommit a6067268a04d
Configured hub: hub.zcash.caution.coReviewed configuration · current match unconfirmedHub’s own check:Evidence verified Configuration does not prove live routing or hub availability.

Measurements below describe the last attempt. Unsigned source claims are separate from the reviewed build and configuration evidence above.

Deployment source tag; pinned to the reviewed commit. Reviewed build · current match unconfirmed.

Reviewed source commit: a6067268a04d14f9821edf6c83d3bdd94dab3776

Reviewed configuration · current match unconfirmed. Configuration evidence ↗

PCR0: 0dc77beee945df52dc872218f89edd51eb3f437275c97be0fc5ed921e87f30826f2823ca6702e0a92a867aec2b1f1f02
PCR1: 0dc77beee945df52dc872218f89edd51eb3f437275c97be0fc5ed921e87f30826f2823ca6702e0a92a867aec2b1f1f02
PCR2: 21b9efbc184807662e966d34f390821309eeac6802309798826296bf3e8bec7c10edb30948c90ba67310f7b964fc500a
TLS certificate SHA-256: 0c851ce60d2f21f181d0c2e69051def2ec6715c5b6c59c5f3f883f0378a5d244
Attestation document SHA-256: 6a12433a4a18ac4081918093bf51324ee594257315c0361bf57e58534a8924ce
Claimed source commit · unverified metadata: e0c834cc9f1554f04c489639ce377ea0408d417e
Signed timestamp: 2026-10-15 05:45:16 UTC
Last successful evidence and TLS check: 2026-10-08 16:46:05 UTC
Verifier: cipherscan-nitro-v1:ba0d0c57de673c8576c91a8730775a87575f5c10

Canary runs on ZecBlock’s server. Its signing keys are pinned by ZecBlock; the monitor itself is not enclave-attested. Both signatures, target evidence, reproduced measurements and TLS binding are checked separately.

Signed statement ↗Evidence ↗Public signing keys ↗Canary policy ↗Source & verification guide ↗

Registered source ↗Release baseline ↗Endpoint reference ↗Observation JSON ↗

Caution

hub

hub.zcash.caution.co:443

Evidence verified

Enclave evidence: Verified
TLS certificate: Matched
Software release: Unconfirmed

Canary observerAwaiting trusted build measurements

Last attempt 2026-10-15 05:45:16 UTC

Build, configuration & evidence

Build version: Source/build version not confirmed

Measurements below describe the last attempt. Unsigned source claims are separate from the reviewed build and configuration evidence above.

PCR0: c4c173771f88508f409e22d8a0882255be7bf2263aaa4c7e2e5d97404a8ae0198c26e422d565f28b9b7eb1fd2f564d1c
PCR1: c4c173771f88508f409e22d8a0882255be7bf2263aaa4c7e2e5d97404a8ae0198c26e422d565f28b9b7eb1fd2f564d1c
PCR2: 21b9efbc184807662e966d34f390821309eeac6802309798826296bf3e8bec7c10edb30948c90ba67310f7b964fc500a
TLS certificate SHA-256: 691cf8070f997beeabf30ad34b6beffd84bf2bca977eabbf508b5af4cc1f8a0d
Attestation document SHA-256: 8eca732fab7171c8ebd9c75a28348fcda136129a27657f3464aa47705a6e9aac
Claimed source commit · unverified metadata: Not provided for the registered source
Signed timestamp: 2026-10-15 05:45:17 UTC
Last successful evidence and TLS check: 2026-10-15 05:45:16 UTC
Verifier: cipherscan-nitro-v1:ba0d0c57de673c8576c91a8730775a87575f5c10

Endpoint reference ↗Observation JSON ↗

Methodology & limitationsEvidence, software measurements and observer trust.

01 · Fresh enclave evidence

Each check sends a new random challenge. We validate the signed response against the AWS Nitro trust root, check its timestamp and reject debug measurements.

02 · A matching connection

The domain and certificate fingerprint inside the signed evidence must match the HTTPS connection used by our observer.

03 · A separate software check

Release verification needs independently established build measurements. Valid evidence alone does not confirm the expected software or prove that the software is safe.

Canary adds signed observations for endpoints with reproduced build measurements, checked every minute and expiring after three minutes. It runs on ZecBlock’s server with operator-pinned signing keys; Canary’s own runtime is not enclave-attested. Connection warnings remain visible even when a recent signed check passed.

These are periodic observations from ZecBlock, not verification of your wallet’s connection. A passing shim does not establish its hub’s status. Build tags identify reviewed source commits. A matching reproduced configuration can confirm a shim’s configured hub, but does not prove live routing or hub availability. The monitor does not measure transaction privacy, batching or wallet service uptime.

Attestation methodology ↗Verify a build yourself ↗Public JSON API ↗