Protocol and execution
Understand what is signed, what runs deterministically, and what the chain actually commits.
Typed transactions, deterministic state
A signed transaction carries its chain ID, sender DID, nonce, gas settings, timestamp, and typed operation. Admission, authorization, policy checks, and native execution determine whether a transition is accepted.
WASM contracts run through the ANVIL runtime when contracts, WASM, and execution policy are enabled. System contracts gate privileged transitions while native handlers mutate state.
Keep execution boundaries explicit
Training, inference, transport, and application UI run outside deterministic consensus. Sigil records the relevant commitments, permissions, receipts, and settlement transitions. A commitment is evidence about bytes and attribution, not a universal correctness proof.
Types do not establish availability
A transaction enum or method name is an interface surface. The active executor, feature build, genesis policy, and activation gates determine what is accepted. Direct treasury, certain identity lifecycle, and payment-channel variants remain gated in the inspected executor.