Ed25519 signatures
Transactions and consensus messages use signatures to bind actions to their signers. Verification checks the actual signed transcript.
Primitives with distinct purposes
Sign the action. Bind the bytes.
Understand the signatures, content hashes, and Merkle commitments that connect Sigil transactions to verifiable records.
CryptographyIllustrated study
Source / fingerprint / attribution
An anchor identifies a record. It does not prove every claim.
01 / Built for a purpose
Use the right claim for each proof.
A signature establishes authorship under a key. A content hash binds bytes. A Merkle proof connects a record to a root. Sigil combines these primitives, while keeping their guarantees distinct from zero-knowledge or full computation proofs.
BLAKE3 content commitments
Code, documents, artifacts, and other records can be identified by their content digest. Recomputing the digest checks that the bytes match the commitment.
Domain separation
Signing and hashing contexts distinguish transactions, consensus phases, and other record types. This prevents valid material from one purpose being casually reused for another.
Merkle inclusion
Structured commitments support proofs that a particular record belongs to a committed set or state. The verifier needs the correct root and proof path.
A staged proof roadmap
Succinct computation proofs are a separate roadmap. Current signed block commitments should not be described as a shipped ZK verifier.
The details matterGood questions.
Good questions.
Clear answers.
Does hashing a document prove its contents are true?
No. It lets someone with the document check that the bytes match a prior commitment. Truth, quality, and authority require additional evidence.
Is FROST external-chain signing available just because it appears in the architecture?
No. Threshold-signing integrations require their own implementation, key ceremony, review, and activation. A named primitive does not establish an available custody service.
Keep exploringOne capability.