One attestation
- Registry
- https://dpp-resolver.bsvb.net
- Attestation
- anchor-probe-2026-07-27/probe-1
- Passport
- anchor-probe-2026-07-27
- Representation
- legacy-uora-json ()
- Digest the registry states
- 26d76f9714ad94725f8f2076c126f10bd3504bb6af6b807c639b313fa97343e8
- Anchor
- 471982d559c5aba35dbf63485489a8f27ccbdc24ed0d88e4ed64b18864869986 output 0,
Checks 3 hold, 3 not established, 1 does not apply
- holds
The stored bytes match their digest digest
SHA-256 of the canonical bytes is 26d76f9714ad94725f8f2076c126f10bd3504bb6af6b807c639b313fa97343e8
- does not apply
The claim's signature verifies claimSignature
a historical UORA record carries no signature of its own; its anchor names the issuer
- holds
The anchor transaction is on chain anchorTransaction
the public source serves 471982d559c5aba35dbf63485489a8f27ccbdc24ed0d88e4ed64b18864869986.0
- not established
The anchoring service's signature verifies anchorSignature
uora-anchor-v1 is a historical format whose layout the standard does not document (spec/legacy-uora-anchor-v3.md covers v3 only), so it cannot be decoded here
- not established
The anchor commits to these bytes and this claim anchorBinding
the anchor was not decoded
- holds
The anchor is in a block inclusion
the WhatsOnChain merkle proof leads to the merkle root of block 959622
- not established
The anchoring service is the one this registry names anchoringService
the anchor was not decoded
The secured bytes, as the registry holds them
{
"passportId": "anchor-probe-2026-07-27",
"recordId": "probe-1",
"timestamp": "2026-07-27T01:30:00.000Z",
"uora_type": "Origin"
}
Shown indented for reading; the digest is taken over the exact bytes the registry returned. Chain evidence from WhatsOnChain.