A precise byte commitment
The anchor carries a content digest. Anyone who later obtains the artifact can hash it and compare the result with the recorded value.
A durable reference for the work
Put a signature and a block behind the artifact.
Anchor an artifact’s digest to a Sigil identity and block so anyone with the bytes can check the same integrity reference later.
Evidence AnchoringIllustrated study
Source / fingerprint / attribution
An anchor identifies a record. It does not prove every claim.
01 / Built for a purpose
A result should leave a checkable record.
An agent finishes a task. A team publishes an audit bundle. A model run produces a checkpoint. Evidence Anchoring records the artifact’s BLAKE3 digest, attribution, and inclusion context without requiring the artifact itself to live on-chain.
Attribution through the signer
The signed transaction records the anchoring identity. Consumers can distinguish who published the commitment from the storage location that served the bytes.
An inclusion point in history
Successful inclusion places the commitment at a block height. The canonical anchor is the included transaction, with query records making it easier to discover.
A small, useful envelope
A label, optional retrieval URI, bounded metadata, and a client nonce connect the digest to an application workflow without uploading the whole artifact.
Find it by digest
Read-only queries retrieve an anchor or list records for a digest. The SDK supports submission, inclusion confirmation, and verification with explicit failure outcomes.
02 / From intent to outcomeA clear path through
A clear path through
evidence anchoring.
- 01
Hash the artifact
Compute the BLAKE3 digest of the exact bytes you intend to reference.
- 02
Sign and anchor
Submit the digest with a label and unique nonce, then confirm successful transaction inclusion.
- 03
Check it later
Retrieve the record, hash the artifact again, and compare the digest and anchoring identity.
The details matterGood questions.
Good questions.
Clear answers.
Does an anchor prove the artifact is true or correct?
No. It establishes a digest commitment and attribution in chain history. Quality, correctness, and provenance beyond the signer require additional evidence.
Does anchoring store or encrypt the artifact?
No. Store the bytes separately and include a retrieval hint if useful. The anchor’s digest, label, metadata, and identity are public on-chain data.
Keep exploringOne capability.