This page indexes Sigil releases. Each release ships a signed sigil-node binary, the sigil-cli, the four first-party SDKs, and a tagged Mintlify documentation snapshot.

​
Versioning

Sigil follows semantic versioning:
ComponentCadence
MAJORHard fork: state-machine, transaction shape, or consensus changes.
MINORBackwards-compatible protocol features pinned at an activation height.
PATCHOperator-side fixes, observability improvements, dependency updates.
A protocol version bump always corresponds to a node, CLI, and SDK release with matching minor version.

​
v0.1.0 — Mainnet launch

ItemValue
Release date2026-Q2
Chain idsigil-mainnet-1
Activation height0 (genesis)
NotesFirst production release. Full primitive set live; T3 compute settlement opt-in per operator.
Highlights:
  • MACA per-block BFT consensus with Tower epoch finality.
  • AkashaKV durable storage with hourly snapshots.
  • Native primitives: tokens, NFTs, AMM DEX, names, mail, mandates, recovery, compute, labor, Crucible, Vigils, Nova.
  • OAS DID identity with FROST-threshold MHR support.
  • Four-vendor TEE verifier (SEV-SNP, SGX, TDX, Arm CCA), fail-closed by default.
  • Public RPC and direct (no-middlebox) endpoints across mainnet and Evolve canary.

​
Roadmap

VersionTargeted features
v0.2.0IBC integration; cross-chain bridges; dynamic validator-set rotation.
v0.3.0T3 dynamic vendor-collateral fetch; Vickrey second-price SNS auctions; Quote v5 / TD Report v1.5.
v1.0.0First long-term-support release; hard-fork freeze on currency naming and address derivation.
Roadmap items move based on operator demand and audit results. See github.com/l1feai/sigil/discussions for ongoing planning.

​
How to upgrade

  1. Read the release notes for the target version.
  2. Run the launch-readiness scripts: 
    python3 scripts/validate-launch-readiness.py akashakv-pin
python3 scripts/validate-launch-readiness.py pre-genesis-feature-readiness
python3 scripts/validate-launch-readiness.py storage-backend-readiness
  3. Test the upgrade on the Evolve canary first.
  4. Roll the validator fleet behind the canary release on the published activation height.

​
Security advisories

Security advisories are published at security.sigil.ml. Each advisory carries a severity, affected versions, mitigation, and a coordinated-disclosure timeline.