Skip to content
Agreement for the agent economy

Many validators. One settled result.

MACA brings signed proposals, deterministic validation, and stake-weighted agreement together to finalize Sigil blocks.

MACA ConsensusIllustrated study
SHARED RULES. SEPARATE ACTORS.
Shared rules. Separate actors.

Illustrated coordination. No live network activity.

MACA Consensus / An illustrated overview
01 / Built for a purpose

Agreement has to survive disagreement.

Agents need a shared answer about what happened: who paid, which contract ran, and which record became part of history. MACA is Sigil’s consensus protocol for turning validated transactions into a finalized block.

01

Validate before committing

A proposed block must pass the network’s validity checks. Agreement follows validation of the candidate and its state transitions.

02

Quorum by stake

Prevotes and precommits are counted against the active validator set’s stake. A quorum requires strictly more than two-thirds, with safety depending on the protocol’s fault assumptions.

03

A signature for each phase

Proposals, prevotes, precommits, and view changes use separate signing domains. A valid signature from one step cannot simply be replayed as another.

04

A path through failed proposals

Timeout and view-change rules move consensus forward when a proposer fails to produce an acceptable candidate. Operators can inspect the resulting messages and decisions.

05

A configurable election model

Proposer scoring can combine stake, uptime, trust, hardware performance, and participation with a concentration penalty. The model makes its inputs explicit instead of reducing operator selection to a single score label.

06

Identity belongs in the protocol

Validator identities and agent relationships are part of Sigil’s wider architecture. Consensus agreement remains deterministic; language-model judgment does not decide block validity.

02 / From intent to outcome

A clear path through
maca consensus.

  1. 01

    Propose

    The selected proposer assembles and signs a candidate block.

  2. 02

    Prevote and precommit

    Validators check the candidate and exchange phase-specific signatures until the required stake agrees.

  3. 03

    Finalize

    The precommit quorum yields a finalization decision and its supporting signatures.

The details matter

Good questions.
Clear answers.

Does single-block finality mean a fixed number of milliseconds?

No. Finality describes the consensus decision. Observed latency depends on network conditions, workload, and deployment configuration, and belongs in a dated measurement.

Do AI models approve transactions?

Block validity uses deterministic rules. Agent-assisted investigation is a separate client workflow and does not insert nondeterministic model calls into consensus.

Keep exploring

One capability.
A connected platform.

01Consensus in depth02Velocity lanes03Run a validator