Publish by content hash
Register bytecode with its BLAKE3 digest and license metadata. Multiple deployments can reference the same artifact, making the deployed code easy to identify.
Deterministic execution with ANVIL
Give your agent a contract to work with.
Publish content-addressed WASM, deploy a contract identity, and control how it executes, upgrades, and connects to other capabilities.
Smart ContractsIllustrated study
A composition, not a black box.
Compose the primitives. Keep their boundaries explicit.
01 / Built for a purpose
Code, identity, and permissions in one place.
A Sigil contract combines a specific bytecode artifact with a controller, a policy, and an execution context. ANVIL runs the supported WASM deterministically so validators can reach agreement on the resulting state.
An explicit capability surface
A contract declares the host functions it may use. Access to communication, compute, and other capabilities is part of the policy, rather than an implicit permission.
Metered execution
Calls supply arguments and a gas budget. Declared access sets help describe the state a call intends to read and write.
Failure that preserves state
Execution uses an overlay so a trapped call can roll back its state changes. A failed call does not become a partially applied contract operation.
Upgrades with a controller
Upgrade and call policies describe who may change the contract and how. Reference artifacts include fungible tokens, multisig coordination, and vesting.
02 / From intent to outcomeA clear path through
A clear path through
smart contracts.
- 01
Register the artifact
Compile a compatible WASM module and publish its bytecode under the matching content hash.
- 02
Deploy the contract
Choose the controller, policies, permitted host functions, and supported execution context.
- 03
Call and inspect
Submit a signed call, inspect its receipt, and use policy-controlled upgrades when the application changes.
The details matterGood questions.
Good questions.
Clear answers.
Can I deploy Solidity bytecode unchanged?
Sigil’s contract surface is WASM with the ANVIL interface. EVM bytecode is not the same interface; use a compatible contract and the supported deployment format.
Can contracts respond to outside events?
Vigils provides a gated subscription and verified callback path. The contract must opt in, and the subscription needs a supported source, bond, and funded gas tank.
Keep exploringOne capability.