Subscribe with intent
Choose the source, filter, callback method, delivery cap, and optional expiry. The subscription describes exactly what should wake the contract.
Contracts that respond to verified events
When something happens, put the contract to work.
Vigils connects event subscriptions, signed deliveries, and deterministic contract callbacks with explicit proof and spending limits.
VigilsIllustrated study
Input / work / result
Work happens off-chain. Its agreement leaves a record.
01 / Built for a purpose
Turn a verified event into the next action.
An agent workflow often waits for something: a block height, a contract event, or completed compute. Vigils lets a contract subscribe to supported events while keeping observation off-chain and callback execution inside deterministic transaction rules.
Opt-in callbacks
A contract must explicitly accept Vigils callbacks. Existing contracts do not become event recipients merely because the network supports subscriptions.
Ingestors submit the evidence
Staked ingestors observe sources and submit signed event deliveries. The chain checks the configured proof, replay, freshness, and source conditions.
A funded gas tank
The subscription pays ingestor fees and callback execution from its gas tank. An unfunded subscription pauses rather than creating an unlimited spending obligation.
Deterministic execution
Accepted deliveries schedule callbacks through the supported WASM path. Consensus execution does not reach out to an arbitrary URL to decide what happened.
02 / From intent to outcomeA clear path through
A clear path through
vigils.
- 01
Opt in and subscribe
Enable callbacks on the contract and register the supported event source and limits.
- 02
Fund and observe
Fund the gas tank while an ingestor watches for matching source events.
- 03
Verify and call
Submit the delivery proof and execute an accepted callback under the network’s deterministic scheduling rules.
The details matterGood questions.
Good questions.
Clear answers.
Can I subscribe to any website or external chain?
No. Only enabled source types and their required proofs are accepted. Oracle and external-chain sources need their own design, review, and activation.
Should a callback be idempotent?
Yes. Distinct finalized events can represent repeated logical conditions. Design the callback so repeated conditions do not accidentally repeat an irreversible application action.
Keep exploringOne capability.