Aegis builds on Safenet Beta, which had validators both evaluate transactions and attest results. The new architecture separates those roles and adds fees and optional onchain enforcement.
How Transactions Get Through
Safe named OpenCover, BlockSec, Candide and IntentGuard as the Sentinels checking submitted transactions. Validators named in the announcement include Gnosis, Greenfield, Safe Labs and Core Contributors.
Under the protocol rules, Sentinels must agree that a transaction is secure before validators can attest it. Disagreement, an insecure result or an inability to check reliably means no secure attestation and no execution through the normal Guard-enforced path.
The Guard checks that attestation against the exact Safe account, network and transaction. Safe describes it as “formally verified.” A valid attestation is an additional authorization requirement, not a replacement for the account’s required owner signatures.
The block is not permanent: owners can use a separate delayed-execution path without an attestation, including to remove the Guard. The configured delay must expire first.
$SAFE Backs Participation
$SAFE is used for validator staking, delegation, governance and participant incentives, distinct from $USDC check fees. Validator and delegated $SAFE are not currently subject to slashing; validators and their delegators can instead lose rewards for poor participation or signing ineligible results.
Sentinels post 800 $USDC bonds per check. During the launch dry run through the end of 2026, however, each risks only a fee-sized 0.40 $USDC penalty, according to the fee documentation. Longer-term slashing terms are scheduled for review in Q1 2027 and require a SafeDAO proposal to change.