Sigil documentation

MACA consensus

Stake quorum, signed votes, deterministic validation, and commitment form the block agreement path.

From proposal to commitment

A proposal must be validated against the same deterministic rules by the participating validators. Domain-separated signing binds votes to their consensus context; quorum rules determine when agreement is sufficient.

Do not interpret an animated round diagram or an empty-block interval as a universal finality or throughput guarantee. Workload, topology, configuration, and measurement window matter.

Inspect the participating set

Read the validator set and activation status from the selected network. A configured launch target is distinct from the currently returned validator roster.

curl --fail-with-body --show-error --silent --max-time 15 'https://rpc.sigil.ml/rpc' \
  -H 'content-type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"sigil_getValidatorSet","params":{}}'

Execution lanes and epoch evidence

Velocity describes the execution-lane architecture. Tower covers epoch-level evidence and finality concepts. Their implementation and activation boundaries should remain separate from block-consensus marketing claims.

On this page