Permissionless distribution runbook
Step-by-step commands to export, verify, publish, propose, challenge, and execute a distribution.
A final Reality.eth answer reflects what bonded participants accepted. It is not a guarantee that a distribution is correct. Distribution data is informational only, not a warranty or financial advice. Safenet does not custody funds in users’ Safes or control their transaction execution. Rewards are variable and not guaranteed.
Roles and responsibilities
Operators An operator is anyone who runs one or more steps of a distribution. Any Ethereum account or Safe can act as an operator. Different people can run different steps, and several operators can check the same period independently. The runbook provides the proposal and execution as Safe Transaction Builder batches. An externally owned account can submit the same calls one at a time. What operators provide- Gas for the transactions they submit.
- The Reality.eth bond in SAFE for each answer they post. The current minimum bond is listed under Current configuration.
- IPFS publishing and pinning of the distribution package.
rewards.safenet-gov.eth reference to values derived from that package.
Distribution lifecycle
1. Period settlement Reward periods are two weeks long. The first Safenet Aegis period started on 13 October 2026 at 00:00 UTC, and each period starts where the previous distribution ended. A period can be calculated once its Safenet consensus data on Gnosis Chain has settled, shortly after the period ends. 2. Export and independent verification An operator exports the distribution with the open-source tooling. The export reads the previous distribution from therewards.safenet-gov.eth record, applies the reward methodology to public staking, participation, and sanctions data, and produces the package, its IPFS CID, the Merkle root, and the transaction bundles.
The calculation is deterministic. Anyone using the same code version and inputs derives the same CID. Other operators can independently verify the published CID before and after it is proposed.
3. IPFS publication
The operator publishes the package on IPFS and pins it. Anyone can pin a copy. The next period’s export reads this package, so it needs to stay available after the distribution executes.
4. Reality.eth proposal and answer
An operator proposes the distribution on the Reality Module of the Safenet Governance Safe (Mainnet). This creates a Reality.eth question that asks whether the package correctly applies the approved methodology and whether the bundle performs only the permitted distribution actions. The operator then answers Yes and posts the minimum bond.
5. Challenges and finalization
Anyone who reproduces a different result can challenge the answer by posting the opposite answer with at least double the previous bond. Each answer restarts the question timeout. The answer that stands when the timeout elapses becomes final.
6. Cooldown and execution
After a final Yes, execution waits for the cooldown. The cooldown is also the window in which a proposal can be vetoed. Once it has passed, anyone can execute the bundle before the answer expires.
7. Onchain distribution and claim verification
Execution runs a single batch from the Safenet Governance Safe (Mainnet). It transfers the additional SAFE needed to the reward-distribution contract, sets the new Merkle root, and points rewards.safenet-gov.eth to the package CID. The batch is atomic: if any part fails, nothing changes.
Anyone can then check that the onchain Merkle root and ENS record match the package. Recipients claim from the reward-distribution contract with their Merkle proof from the package, directly or through a staking interface. See Distribution and claiming.
Timing
With the current configuration, an unchallenged distribution can execute about 8 days after it is proposed, within a 2-day execution window. Challenges extend this.
Earned, withheld, and claimable rewards
A distribution package records three different amounts:- Earned: rewards calculated for an account under the reward methodology, before sanctions and KYC filters. The package covers Validator and Delegator rewards and also includes Sentinel grants.
- Withheld: earned rewards that are not yet claimable. An account’s payout is withheld if the account requires KYC under the screening and KYC requirements and is not yet approved. An account on a screened sanctions list is left out of the Merkle tree. Withheld amounts stay funded in the reward-distribution contract.
- Claimable: the account’s cumulative amount in the Merkle tree, minus what it has already claimed. When SEF approves an account, the next export moves its withheld amounts into the claimable total.
Safeguards and exceptions
Challenges Anyone holding SAFE can challenge an open question. No arbitrator is configured, so bond escalation is the only way to dispute an answer. Doubling bonds make defending a wrong answer increasingly costly, but the outcome depends on participants who verify the distribution and challenge in time. Invalid or superseded proposals If a proposal’s package or bundle differs from the one the tooling derives, participants should answer No. A final No never executes. A wrong answer that becomes a final Yes stays executable until it expires, unless it is vetoed. Exporting a corrected distribution does not cancel it. Re-asking a question If a question is finalized as Invalid on Reality.eth, the same distribution can be proposed again with a new question. A question finalized No, an expired Yes, or a vetoed proposal cannot be asked again for the same package. Veto The SEF vetoer can invalidate a pending proposal before it executes, only for tax, sanctions, or AML compliance. A veto invalidates the whole bundle: the transfer, the Merkle root, and the ENS record all stay unchanged. It cannot undo an executed distribution. Expiration If no one executes a final Yes within the execution window, the answer expires and the bundle can no longer execute. After expiry, anyone can mark the proposal as invalid on the Reality Module. Monitoring These safeguards work only if participants watch for new questions, answers, and pending executions, and act within the time windows. A wrong answer that no one challenges becomes final.Rewards
Review the reward methodology and claiming.
Governance
Review how proposals execute and the current configuration.
Contracts and audits
Find the Governance Safe, Reality Module, and reward-distribution contract.
Runbook
Run and verify a distribution.