Skip to main content
Safenet Beta is initiated by the Safe Ecosystem Foundation (SEF), which is accountable to SafeDAO governance. The Safenet Beta, the Staking contract, and the Validator network are live and run under SEF’s mandate.The staking rewards mechanism is a proposal currently pending SafeDAO approval. No rewards have been distributed yet. If the proposal passes governance, rewards will be distributed according to the mechanism described in Staking rewards.Configuration changes to the protocol, including any updates to the withdrawal delay, require a timelock before taking effect. Changes to reward parameters require a governance proposal.
The rewards proposal is not yet approved. This page will be updated when the SafeDAO vote concludes.
Yes. The Safenet Beta contracts, Explorer and staking UI are publicly available on GitHub: safe-research/safenetThe Staking contract has been independently audited. The audit report is available in the repository. See Security for the full audit report and contract details.
A technical overview is provided in the Safenet repository.Smart contractsThe full source for the Staking and Consensus contracts is in safe-research/safenet/contracts. Inline documentation covers the key functions, events, and parameters.FROST threshold signingSafenet uses FROST (Flexible Round-Optimized Schnorr Threshold Signatures) for Validator attestations. The standard is defined in RFC 9591.Staking mechanicsThe staking and rewards documentation covers how stake is weighted, how rewards are calculated, and what conditions affect eligibility. Start with Staking.ValidatorsThere is a Validator handbook available.For questions not covered by the documentation, open an issue on GitHub.
The Safenet Beta Explorer is a public interface for observing transaction validation activity on the network. No wallet connection or account is required to view activity.Exploring network activityThe Explorer provides a live stream of Safe transactions that have been proposed to the Safenet Validator set. Each transaction shows its current status (Proposed, Attested, or Timed-out) and a detail page with the full transaction breakdown, Validator participation, and links to Safe{Wallet} and chain explorers.You can search by Safe address or safeTxHash.Submitting a transaction for validationIf your Safe transaction has not yet been proposed to Safenet Beta, you can submit it directly from the Explorer:
  1. Navigate to the Explorer at http://explorer.safenet-beta.eth.limo
  2. Enter your safeTxHash or paste the transaction details manually
  3. Submit - no wallet required, the submission is relayed for you
Under normal network conditions, a transaction moves from Proposed to Attested within a few signing rounds. In practice this is typically a matter of seconds to low minutes.The exact duration depends on two factors. First, Validator participation: if enough Validators are online and responsive, the FROST threshold signature completes in a single round. If some Validators are slow or offline, the signing coordinator retries until quorum is reached or the round times out. Second, network conditions: latency between Validators affects round-trip times for the threshold signing protocol.You can monitor the status of any transaction in the Explorer. A transaction that reaches Timed-out did not receive enough Validator signatures within the signing window. You can resubmit it for a new signing round.
Safenet Beta only does basic transaction security checks. It is a Beta product and might misbehave.
Check the attestation status in the ExplorerLook up your transaction by safeTxHash in the Explorer. The status field shows one of three states:
  • Proposed: the transaction has been submitted to the Validator set and a signing round is in progress.
  • Attested: a threshold of Validators produced a FROST signature over the transaction. This signature is recorded onchain on Gnosis Chain.
  • Timed-out: the signing round did not reach quorum within the allowed window. The transaction can be resubmitted.
What “Attested” meansAn attested transaction has a threshold FROST signature from the active Validator set. FROST is a standard threshold signing scheme (see RFC 9591). It means no single Validator approved the transaction alone: a defined minimum number of independent Validators all participated in producing the signature.The signature and the signed message are stored in the Consensus contract on Gnosis Chain. Anyone can retrieve and verify the signature against the Validator set’s public key using standard cryptographic tools.Checking onchain
(bytes32 msg, FROST.Signature memory sig) = consensus.getRecentAttestation(tx);
See the Consensus contract documentation for the full verification flow.
In Safenet Beta, the Validator set is permissioned. Validators are selected and onboarded by the Safe Ecosystem Foundation. The Validator set is intentionally small in Beta to allow the core staking, consensus, and FROST threshold signing mechanics to be proven out in a controlled environment.If you are interested in running a Validator node in a future phase, watch the Roadmap for updates on when the Validator set opens up and reach out.
Transactions are submitted to the Consensus contract on Gnosis Chain via the proposeTransaction function.
// Submit a transaction for validation
bytes32 message = consensus.proposeTransaction(tx);

// Listen for the TransactionAttested event, then retrieve the signature:
(bytes32 msg, FROST.Signature memory sig) = consensus.getRecentAttestation(tx);
The tx parameter is a SafeTransaction.T struct containing the standard Safe transaction fields. After calling proposeTransaction, listen for the TransactionProposed event to confirm submission, then wait for TransactionAttested before using the resulting FROST signature.Events to listen for
  • TransactionProposed(bytes32 indexed safeTxHash, ...): emitted on successful submission
  • TransactionAttested(bytes32 indexed safeTxHash, FROST.Signature sig): emitted when threshold signing completes
See the Consensus contract source for the full interface and struct definitions.
For questions not covered here, reach out at research+safenet@safe.dev.