Skip to main content
Safenet uses smart contracts across Gnosis Chain, Ethereum Mainnet, and the networks where the Safenet Guard is deployed. This page provides references for deployed contracts, source code, governance accounts, and completed security reviews.

​
Deployed contracts

The Staking and reward-distribution contracts are carried forward from Safenet Beta.
TODO: Add contract addresses and audit reports for SentinelOracle, Consensus, FROSTCoordinator, and SafenetGuard once deployed. Replace source links to main/beta with links to the exact release tag or commit corresponding to the deployed Safenet Aegis version. Core protocol The core Safenet protocol contracts run on Gnosis Chain:
  • SentinelOracle coordinates Sentinel checks, fees, bonds, arbitration, and configurable protocol parameters.
  • Consensus coordinates Validator attestations and Validator-set epochs.
  • FROSTCoordinator coordinates Validator FROST signing ceremonies.
The canonical Safenet Oracle will be identified through oracle.safenet-gov.eth. SafeDAO can change configurable SentinelOracle parameters without replacing the Oracle, including:
  • Sentinel set.
  • Transaction-check fee.
  • SafeDAO fee share.
  • Bond parameters.
  • SafeDAO fee receiver.
Changes to immutable Oracle configuration require deployment and activation of a new Oracle. See Governance for Oracle governance and upgrades. Safenet Guard The Safenet Guard verifies Safenet attestations and can require a valid secure attestation before normal Safe execution. Guard contracts are deployed on the execution networks where Guard enforcement is supported. A Safenet Guard deployment is configured with the Safenet consensus context and delayed-execution parameters at deployment. Changes to this configuration require a new Guard deployment. TODO: Add the final Guard deployment addresses for each supported network. See Safenet Guard for the enforcement model. Staking and reward distribution The Staking contract on Ethereum Mainnet manages SAFE staking, delegation, withdrawal configuration, and the active Validator set. The contract is non-upgradeable. Its SAFE token and configuration-change delay are fixed at deployment. The contract owner can propose changes to the withdrawal delay and active Validator set, subject to the contract’s configuration delay. Validator and Delegator rewards are distributed through the reward-distribution contract on Ethereum Mainnet. See the table above for its address, source, and audit. See Staking and Rewards.

​
Governance accounts

Safenet uses separate Safe accounts for protocol governance, arbitration, and reward distribution. TODO: Add addresses for the SafeDAO Safenet Safe, Safenet Security Council Safe, and Reward Distribution Safe once deployed. The SafeDAO Safenet Safe on Gnosis Chain is the governance address configured in the Safenet Oracle and is also the SafeDAO fee receiver. The Safenet Security Council Safe on Gnosis Chain resolves arbitration when Sentinel decisions are split. The Reward Distribution Safe on Ethereum Mainnet publishes accepted reward distributions. See Governance and Rewards for the corresponding processes.

​
Report a security issue

See Bug bounty for how to report a security issue.