MACA finalises a block. Tower finalises an epoch.
Tower stacks 256 finalised blocks into one epoch plate and drives a ⅔ stake-weighted locking pin straight through the stack. Cross-zone economic finality on top of MACA's single-block consensus — Casper-FFG style, slashable by surround vote.
Two finality layers
MACA finalises a block. Tower finalises an epoch.
MACA gives single-block finality inside a zone: four signed rounds and the block is done. Tower is the long-range layer that stacks 256 finalised blocks into one epoch plate, and drives a locking pin through the stack so the epoch is economically committed-to across zones.
TowerRegisterValidator
Stake for the epoch chain.
Tower runs as its own validator set with its own bonded stake — separate from MACA's BP/BV split. TowerRegisterValidator binds the operator DID to a Tower signing key and posts MINT as the locking-pin collateral. The validator joins the quorum at the next epoch boundary.
TowerFinalityVote
Stack the plate.
At every epoch boundary, Tower aggregates the 256 finalised headers into one epoch root and broadcasts a Casper-FFG style (source → target) vote. Each validator's signature lands on the plate as a coloured slot — every signed plate climbs the tower.
The locking pin
⅔ weighted attestation drives it home.
The plate is not finalised the moment it is stacked — it is finalised the moment the locking pin slots through. ⅔ of Tower stake is the threshold. Once the pin lands, the previous plate becomes finalised; a reorg past it would require a coordinated supermajority slashing event.
TowerSubmitEvidence
Two votes, same epoch. Burn the bond.
If a validator signs two different epoch roots at the same height (equivocation), or signs a vote whose source/target span surrounds an earlier vote (a Casper-FFG surround vote), any other node can submit the two signatures as evidence. The chain re-verifies both signatures and burns 100% of the offender's Tower bond.
Slashed plates drop
The bad plate falls out. The stack closes.
The slashed validator is removed from the locking quorum at the next epoch boundary. Its plate falls out of the stack; the remaining plates close the gap. The locking pin re-weights, and the tower keeps stacking — minus the operator who broke the rules.
TowerClaimRewards
Harvest the epoch payout.
Operators call TowerClaimRewards once an epoch is finalised. Rewards stream proportionally to signed-vote count, weighted stake, and time-in-set. Delegators share pro-rata. The chain's economic security comes from honest validators stacking honest plates, epoch after epoch.
Seven typed transactions
Seven calls. One epoch chain.
TowerRegisterValidator, TowerUpdateValidator, TowerExitValidator, TowerFinalityVote, TowerSubmitEvidence, TowerDelegateStake, TowerClaimRewards. Each one signed under a Tower-specific domain prefix so votes can never replay as MACA precommits.
TowerRegisterValidator
Stake for the epoch chain
TowerUpdateValidator
Rotate keys, adjust stake
TowerExitValidator
Unbond and leave
TowerFinalityVote
Stack the plate
TowerSubmitEvidence
Call out equivocation
TowerDelegateStake
Stake without operating
TowerClaimRewards
Harvest the epoch payout
Two safety violations
Equivocate. Surround. Lose the bond.
Tower's slashing surface is small on purpose. Two conflicting votes at the same epoch — or a vote whose source/target span surrounds an earlier one — and the chain burns 100% of the offender's Tower bond. Evidence is re-verified locally; there is no oracle.
Stack the epoch. Drive the pin.
Register a Tower validator, bond MINT, sign every epoch, and earn rewards for keeping long-range finality alive. The locking pin lands every 256 blocks — the chain rewards the operators who hold the stack together.