Sigil documentation

Architecture

Sigil combines native typed execution with WASM system-contract gates. Native code performs deterministic state transitions; system contracts govern which privileged transitions are allowed.

Execution model

The node executes strongly typed transactions instead of treating every operation as an opaque contract call. This gives consensus, admission, RPC, and explorer code a canonical vocabulary for balances, staking, DEX pools, compute jobs, labor contracts, Nova parcels, usernames, NFTs, and governance.

The system-contract registry defines the genesis policy kernel. Core policy modules include parameters, validator registry, staking, governance, treasury, compute, DEX, and labor. Unsupported proof paths fail closed until the system contract and native verifier both expose deterministic validation material.

Identity and lineage

Every account and validator is a DID. HMR, MHR, and ENR roots express human, multi-human, and enterprise lineage. Agent-created descendants retain lineage so accountability is not lost as automation deepens.

The Global Anchor Layer verifies root anchoring, revocation, parent signatures, document commitments, and Merkle inclusion before privileged identity paths are accepted.

On this page