A rollup customer chooses an execution stack and data-availability and settlement layers. In the designed bundle, SQUAD sequencers order transactions, VITAL operators check the resulting state, and MACH operators sign confirmations that applications can treat as economically backed before base-layer finality. Slashing can punish conduct covered by the AVS rules; it cannot repair every software bug, bad configuration or outage.
The implementation record is narrower than the architecture diagram. The official MACH repository, archived in June 2026, records six named mainnet service-manager deployments. Its BLS path separates operator, verifier and signature aggregator, while the ZK path verifies proofs without that aggregator. The operator-setup repository requires prior admission. A customer therefore has to identify the deployed mode and contracts rather than assume that every MACH instance uses the same components.
ALT staking is a separate contract path. A user deposits ALT for stALT and can convert stALT into reALT for delegation to launch pools. The live staking FAQ says leaving the reALT vault for stALT has no unbonding period; the documented 21-day reward-free cooldown begins only when stALT is redeemed for underlying ALT. In BLS MACH, the whitelister changes operator entries while the owner can replace that whitelister, toggle the allowlist, change supported rollup-chain IDs, set the confirmer and alter the quorum threshold. In ZK MACH, the owner directly changes the operator allowlist. ProxyAdmin can replace implementations, but the archived repository does not by itself identify the current beneficial controller of every deployed ProxyAdmin.
The token contract itself is capped at 10 billion ALT. Its Safe owner can pause transfers and mint up to that cap. Supply was already at the cap and transfers were unpaused at review, but a later burn could create minting room within the cap.