Vigils: event-driven contracts.
A verified event delivery schedules a deterministic callback in the next block.
1. Opt in and subscribe
The contract opts in with accepts_vigil_callbacks. A subscriber registers an event filter and the required bond and gas funding. Allowed source kinds and activation height are controlled by chain policy.
2. Submit evidence from an ingestor
Ingestors observe sources off chain and submit signed EventDelivery records. Validators check source policy, proof material, replay protection, gas, and bond requirements. External network calls are not performed in consensus execution.
3. Execute in canonical order
Accepted deliveries schedule callbacks in the canonical next-block order. The callback remains deterministic and subject to the contract and chain execution rules. The contract can react autonomously without giving up replayable state transitions.
Inspect subscriptions and delivery history
The RPC catalog includes subscription, ingestor, and delivery-history queries, along with separately authorized lifecycle methods. Method presence does not bypass contract opt-in, feature builds, source allowlists, or activation policy.
Treasuries: design and boundaries.
A design reference for policy-controlled funds. Direct public treasury transactions remain gated in the inspected executor.
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.