Safe Launches Safenet Beta to Give SAFE Token a Staking Role in Network Security

Safe Launches Safenet Beta to Give SAFE Token a Staking Role in Network Security

N
News Editor 01
2026-07-09 13:26:13
Safe has unveiled Safenet Beta, allowing SAFE holders to delegate stake to genesis validators and help secure the network. The move expands SAFE beyond governance into an active security role.
SafeSafenetSAFE stakingon-chain securitysmart accounts

Safe Ecosystem Foundation announced the launch of Safenet Beta at EthCC in Cannes, introducing the first live network-security use case for the SAFE token beyond governance. Under the beta framework, SAFE holders can delegate to genesis validators and, subject to governance approval, earn staking rewards for helping secure the network.

Safenet is designed as a decentralized transaction security network that enforces checks at the protocol level before a Safe transaction can be executed. Rather than relying on centralized warning systems or off-chain heuristics, the system uses cryptographic attestations that are verified on-chain. Safe said its protocol has processed more than $1.4 trillion in total value, making pre-execution security a notable infrastructure expansion.

How the system works

When a transaction is proposed, independent validators review it against a defined set of security rules. If the transaction passes, they generate a cryptographic attestation. A Safe Guard installed on the user’s Safe account then verifies that attestation on-chain before execution. Without a valid attestation, the transaction does not proceed. According to the announcement, the network is Byzantine fault tolerant and can continue producing correct attestations even if up to one-third of validators act dishonestly.

Safe also said users retain full control over their funds. If a transaction fails to meet attestation requirements but the owner still wants to proceed, execution remains possible after additional explicit approval and a waiting period. The design aims to preserve self-custody while adding protocol-enforced security checks.

What is included in the beta

Safenet Beta launches with six genesis validators: Greenfield, Gnosis, Safe Labs, Rockaway, Blockchain Capital, and Core Contributors GmbH. Each validator is required to stake at least 3.5 million SAFE. The beta includes static transaction checks aimed at blocking common attack vectors, a staking interface for delegation by SAFE holders, and a real-time attestation explorer.

The initial transaction checks cover unauthorized or unexpected code execution through delegatecalls, installation of untrusted modules, and attempts to alter or bypass Safe account security settings. Safe added that more advanced checks, slashing, and fee-based rewards are planned for later phases.

SAFE moves beyond governance

The rollout marks a structural shift for the token, with SAFE taking on an economic role in network security. Validators stake SAFE to run the network, while delegators back those validators through staking. Safe said its long-term ambition is for all value processed through Safe to be secured by Safenet.

At the same time, the announcement included clear caveats. Delegation can already be completed through the Safenet interface without additional infrastructure, but withdrawals are not on-demand and smart contract risk remains. Staking rewards are still pending SafeDAO approval under SEP-55. The foundation also stated that Safenet Beta is provided on an “as is” basis for development and testing, and users interact with it at their own risk.

This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan.
200

Disclaimer:

The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.

Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.