Authenticate the action
Signatures, network binding, and nonces establish the transaction’s context. Consensus votes additionally bind their phase and round.
Trust boundaries made explicit
Every permission has a boundary.
Explore Sigil’s identity checks, deterministic execution, transaction validation, receipt verification, and operational security boundaries.
Security ModelIllustrated study
Defined scope / checked / bounded
A permission is a condition, not a blank cheque.
Security Model
01 / Built for a purpose
Ask what each layer is allowed to trust.
An agent can be correctly identified and still attempt an unauthorized action. A signed result can still be wrong. Sigil’s security model separates identity, permissions, execution, and evidence so applications can check the claim relevant to each step.
Check the authority
Supported identity and GAL flows verify anchors, lineage, and revocation. Application permissions and mandates need an active enforcement path beyond identity alone.
Constrain execution
WASM metering, explicit host capabilities, and rollback behavior limit what a contract call can do and how failure affects state.
Reject unsupported verification
Compute and event policies require the necessary proof and trust material. Missing verifiers or disabled sources do not silently become accepted receipts.
Investigate outside consensus
Anomaly rules and validator-agent research use explicit snapshots and budgets. Nondeterministic model investigation remains separate from block-validity decisions.
Operate the boundary
Key custody, network access, immutable releases, recovery procedures, and independent review matter alongside cryptographic design. They require evidence from the actual deployment.
The details matterGood questions.
Good questions.
Clear answers.
Does this page mean Sigil has a completed independent audit?+
No. Architecture, internal testing, formal models, and independent audit reports are different forms of evidence. Audit completion should be established by the relevant published report and scope.
Can I rely on one verification badge for all work?+
No. Identity, signatures, sampled inference commitments, hardware attestation, and execution proofs answer different questions. Match the verification policy to the consequence of the action.
Keep exploringOne capability.