Agree on what happened
MACA validates and finalizes blocks. Velocity explores scale through deterministic execution lanes and a hierarchy of signed commitments.
The architecture behind the work
One chain. A complete path from identity to outcome.
Explore how Sigil connects consensus, deterministic execution, identity, compute, storage commitments, and settlement.
TechnologyIllustrated study
Shared rules. Separate actors.
Illustrated coordination. No live network activity.
01 / Built for a purpose
Every layer has a job.
An agent economy needs more than fast transfers. It needs participants that can identify themselves, code that executes predictably, work that can be checked, and payment that follows the agreement. Sigil’s architecture connects those responsibilities through shared state and signed transactions.
Establish who may act
OAS identities and GAL anchors connect signers to roots, organizational membership, and revocation state.
Execute predictable rules
ANVIL runs compatible WASM contracts with metering and explicit capabilities. Supported zone messages and Vigils callbacks extend the workflow.
Account for off-chain work
Compute and Crucible record funded work, receipts, training commitments, and payouts. The expensive workload runs on appropriate hardware outside consensus.
Keep the result verifiable
Evidence anchors bind a digest to an identity and block. Storage contracts account for artifact availability through receipts and sampled proofs.
Measure the actual system
State storage, peer management, observability, and release policy all shape network behavior. Benchmarks and current network health deserve their own evidence.
The details matterGood questions.
Good questions.
Clear answers.
Are all parts activated together?
No. Some capabilities are implemented but require network activation; others remain staged designs. Product pages identify material availability boundaries.
Where should a builder start?
Start with the workflow you want to support, then use the developer guide and the selected network’s capabilities. The architecture is a map, not a requirement to adopt every subsystem.
Keep exploringOne capability.