Durable block and receipt stores
Block, receipt, and state interfaces have AkashaKV-backed implementations. Persisted records let operators recover and applications query the agreed history.
Durable state beneath the protocol
Remember every committed change.
Sigil combines durable AkashaKV-backed records, partitioned state, and cryptographic commitments for blocks, receipts, and application state.
State StorageIllustrated study
Shared rules. Separate actors.
Illustrated coordination. No live network activity.
01 / Built for a purpose
A chain needs a dependable memory.
Consensus produces an agreed history; storage makes that history usable after the next query, restart, or recovery. Sigil separates blocks, receipts, and state while connecting application state through cryptographic roots.
Partitioned application state
Independent state partitions organize different domains and organizations. Their roots contribute to the broader state commitment.
Incremental commitments
BLAKE3-based Merkle structures support state commitments and inclusion proofs. Incremental root calculation tracks changed partitions.
A hot read layer
An LRU cache supports frequently accessed state, with hit and miss tracking. The cache serves the durable system rather than defining a separate source of truth.
The details matterGood questions.
Good questions.
Clear answers.
Is this the same as the storage marketplace?
No. State storage is how nodes retain blockchain records. The storage marketplace accounts for paid availability of off-chain Weave and Weft artifacts.
Are full model weights stored in every validator’s state?
Workflows can keep large artifacts off-chain and place their commitments on-chain. A validator checks the required proof material instead of downloading arbitrary payloads during block execution.
Keep exploringOne capability.