# \[1IP-XX\] Fund the Governance Defense Safe with 2.5 ETH to Formalize and Automate Reality Module Defense **URL:** \ **Category:** 2.0 1inch DAO\ **Created:** [September 24, 2026, 2:57pm UTC](https://gov.1inch.network/t/1ip-xx-fund-the-governance-defense-safe-with-2-5-eth-to-formalize-and-automate-reality-module-defense/1006 "2026-09-24T14:57:48Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![0xpranav](https://sea1.discourse-cdn.com/flex001/user_avatar/gov.1inch.network/0xpranav/32/153_2.png) [@0xpranav](https://gov.1inch.network/u/0xpranav)\ **Post date:** [September 24, 2026, 2:57pm UTC](https://gov.1inch.network/t/1ip-xx-fund-the-governance-defense-safe-with-2-5-eth-to-formalize-and-automate-reality-module-defense/1006/1 "2026-09-24T14:57:48Z")
## Simple Summary - Transfer 2.5 ETH from the primary 1inch DAO Treasury to a dedicated 2-of-3 Governance Defense Safe used exclusively to post “Invalid” bonds and pay Kleros arbitration fees when a malicious proposal is submitted to the 1inch Reality Module. - Adopt a written, pre-agreed defense playbook (decision rules, funding, coverage, automation) so the response to an attack is no longer improvised. - Return all net proceeds from won escalation games to the DAO Treasury every year, and return the full remaining balance if the playbook is retired. ## Abstract The 1inch DAO executes passed Snapshot votes on-chain through the Zodiac Reality Module (SafeSnap). Anyone can submit a proposal to that module and bond “Yes” on Reality.eth; the DAO’s only defense before finalization is to bond “Invalid” and, if necessary, escalate to Kleros arbitration. Currently, this defense is being exercised via ad-hoc coordination. This proposal funds a dedicated 2-of-3 Defense Safe with 2.5 ETH (2.0 ETH bond reserve, 0.5 ETH arbitration reserve), formalizes the decision rules for bonding and escalation, and activates a monitoring bot that detects `addProposal` calls, verifies them against Snapshot, and pre-composes counter-bond transactions for the signers to review and execute. The ETH is a working float, not a grant: bonds are returned when the DAO’s answer finalizes, the attacker’s forfeited bonds are swept back to the Treasury annually, and the full balance is returned if the DAO retires the playbook. ## Motivation In the current process: - Detection is automated but everything after it is improvised. There is no written rule for when to keep bonding versus when to escalate to Kleros, so whoever is online decides under time pressure, often at unsocial hours. The current detection layer (an OpenZeppelin Defender Sentinel) is also being deprecated. - The ETH used for bonds comes from whichever teammate is available, after discussion. That is slow, unaccountable, and puts personal funds at risk on the DAO’s behalf. - Nothing about the response is repeatable or auditable. ## Specification ### 1. Funding transfer | Field | Value | | --- | --- | | From | Primary 1inch DAO Treasury: `eth:0x7951c7ef839e26F63DA87a42C9a87986507f1c07` | | To | Governance Defense Safe: `eth:0xE10a1A873a780B5E69f7cD5DA5dA31a1fC528Eb8` | | Asset | ETH | | Amount | 2.5 ETH | | Method | SafeSnap “Transactions” container on the Phase 4 Snapshot vote (transfer funds) | **Precondition for execution.** The Defense Safe must be configured 2-of-3 with the signers listed below before the transfer executes. This is verifiable on-chain by anyone, including the Treasury multisig owners during the 72-hour Timelock. ### 2. Governance Defense Safe | Field | Value | | --- | --- | | Address | `0xE10a1A873a780B5E69f7cD5DA5dA31a1fC528Eb8` (Ethereum mainnet) | | Threshold | 2-of-3 | | Signers | spindoctor, Belac, Tanz0rz | | Permitted use | `submitAnswer` “Invalid” bonds on 1inch Reality Module questions; Kleros arbitration requests on those questions; `claimMultipleAndWithdrawBalance` to recover bonds; gas for the above; annual return of proceeds to the Treasury | | Prohibited use | Anything else. In particular, no bonding on non-1inch questions and no “Yes” bonds | ### 3. Budget | Line | Amount | Purpose | | --- | --- | --- | | Bond reserve | 2.0 ETH | Counter-bonds. The standard two-round ladder locks up to 1.0 ETH per incident (0.2 + 0.8 ETH); each bond is a separate deposit that stays locked until the question finalizes, so the reserve is sized for an attacker who opens above the minimum bond or for two overlapping incidents. | | Arbitration reserve | 0.5 ETH | One Kleros arbitration request. The DAO Treasury docs put the current fee at 0.36 ETH (5 jurors x 0.072 ETH); the remainder is buffer for fee changes and gas. | | **Total** | **2.5 ETH** | | ### 4. Decision rules Reality.eth requires each new answer to post at least 2x the previous bond. The 1inch module’s escalation timeout is 72 hours and resets on every new bond. **Rule:** the Defense Safe posts at most two “Invalid” bonds per question. If the attacker bonds “Yes” a third time, the team requests Kleros arbitration instead of bonding again. Requesting arbitration pauses the escalation game and removes the question from the bond ladder entirely. Reactive case (attacker answers first): | Round | Attacker “Yes” | Our “Invalid” | Action | | --- | --- | --- | --- | | 1 | 0.1 ETH | 0.2 ETH | 1st “Invalid” bond | | 2 | 0.4 ETH | 0.8 ETH | 2nd “Invalid” bond | | 3 | 1.6 ETH | none | Request Kleros | Preemptive case (the bot detects `addProposal` before any answer exists and opens the question with “Invalid” at the minimum bond): | Round | Our “Invalid” | Attacker “Yes” | Action | | --- | --- | --- | --- | | 1 | 0.1 ETH | 0.2 ETH | 1st “Invalid” bond opens the game | | 2 | 0.4 ETH | 0.8 ETH | 2nd “Invalid” bond | | 3 | none | none | Request Kleros | ### 5. Coverage and escalation - The support team collectively monitors this and the first teammate to see an alert verifies and rallies other signers. - Existing high-severity alerts remain in force and are treated as such. If the bot or the Defense Safe is unavailable, teammates may still answer with a personal wallet; the DAO’s protection does not depend on the Safe alone. - Independently of this playbook, the DAO retains its two existing backstops: anyone may request Kleros arbitration at any time after the first answer, and the Security Council may veto any execution 7-of-12 during the 72-hour Timelock. ### 6. Defense bot (advisory only) The bot listens for `addProposal` events on the 1inch Reality Module (`0xa62D2a75eb39C12e908e9F6BF50f189641692F2E`) and, for each proposal: 1. Confirms the referenced Snapshot proposal exists and passed. 2. Verifies every on-chain transaction hash against the Snapshot SafeSnap payload using the module’s own `getTransactionHash` view, catching mismatched `to`, `value`, `data`, `operation`, and `nonce`. If verification passes, it posts a “legitimate” notice and does nothing on-chain. If it fails, the bot composes the next valid `submitAnswer(question_id, 0x00, max_previous)` counter-bond at 2x the current top bond and proposes it to the Defense Safe. It tracks re-bonds and proposes the second counter-bond under the same rules; beyond the two-bond limit it tells the team to request Kleros. When an “Invalid” answer finalizes, it composes `claimMultipleAndWithdrawBalance` so bonds and the attacker’s forfeited stake are recovered. The bot holds no keys and cannot move funds. Every on-chain action requires two of the three signers to review and execute. All bot activity is posted to `#governance-reality-eth` with links to the relevant proposals and transactions. ### 7. Return of proceeds and wind-down **Annual sweep.** At the end of each year, the Defense Safe transfers to the primary DAO Treasury any balance above the 2.5 ETH operating float. This captures forfeited attacker bonds and Reality.eth question rewards from won games, net of gas and arbitration fees actually paid. **Top-up.** If losses or fees bring the balance below what the decision rules require, the authors return to the DAO with a new proposal; the Safe is never topped up unilaterally. **Wind-down.** If the scoped veto role (or any successor mechanism) makes this playbook unnecessary, or the DAO votes to retire it, the full remaining balance is returned to the Treasury within 30 days. The DAO cannot compel a return from a Safe it does not control, so return depends on the named signers acting. If the balance is not returned within that window, or if the Safe is unreachable because signers have become inactive, the DAO may treat the outstanding amount as a recoverable obligation of the signers and pursue it through the dispute-resolution route in the Guidelines. This residual dependency is accepted as proportionate to a 2.5 ETH float. ## Rationale **Why a dedicated Safe rather than personal wallets.** Personal wallets are the status quo but they are slow to coordinate, put contributors’ own ETH at risk, and leave no clean record of DAO funds. A 2-of-3 Safe with a fixed purpose is auditable and bounded. **Why 2-of-3 rather than a larger multisig.** Bonds must land within the 72-hour escalation window. Two of three named signers is the smallest threshold that still requires more than one person’s approval, while staying reachable within that window. **Why cap at two bonds and then arbitrate.** The bond ladder is a delay tactic that makes an attacker fold cheaply; it is not where the treasury is ultimately protected. Kleros resolves on the truth of the question rather than on who has more ETH, and requesting it pauses finalization. Capping bonds keeps the DAO’s exposure bounded and predictable and avoids a bidding war against an attacker whose payoff is the treasury itself. **Why 2.5 ETH.** 1.0 ETH covers the standard two-round ladder; 2.0 ETH gives headroom for a higher opening bond or a second concurrent incident. 0.5 ETH covers one arbitration at the documented rate plus buffer. Every bond is recoverable when the DAO’s answer finalizes, so the true expected cost to the Treasury is gas and any arbitration fee, offset by forfeited attacker bonds. **Why an advisory bot rather than an autonomous one.** Verification depends on an off-chain data source (Snapshot). A bot that could bond autonomously would turn any false positive into a self-inflicted bond against a legitimate proposal. Keeping humans on the signature step preserves speed where it matters (detection and transaction composition) while keeping a person accountable for every on-chain move. **Alternatives considered.** Continuing ad-hoc (rejected: not repeatable, personal funds at risk). Waiting for the scoped veto role (rejected: leaves a known, exercised attack path uncovered in the interim). A larger reserve (rejected: no benefit, since the rules stop at two bonds). ## Considerations ### Security - **Exposure is bounded.** At most 2.5 ETH is ever at risk, and only when the Defense Safe has actively bonded. Bonds are forfeited only if the DAO’s “Invalid” answer is ultimately wrong; the rules restrict the Safe to bonding “Invalid” on 1inch questions that fail verification. - **The bot cannot move funds.** It composes transactions; it does not sign them. Compromise of the bot cannot drain the Safe. Signers are expected to independently verify every proposed transaction against the Reality.eth question and the Snapshot proposal before signing, and this is written into the playbook. - **The Safe must be 2-of-3 before funding.** The transfer is conditioned on the Safe’s on-chain configuration matching this proposal at execution time; the Treasury multisig can verify this during the Timelock and veto if it does not. - **Hardening before activation.** The authors have completed an internal security review of the bot and playbook and identified a small number of hardening items in the bot’s verification and state-tracking logic. These will be completed before the bot is switched to active proposing on mainnet; until then it runs in notify-only mode. Specific details are withheld from this public post to avoid tipping current weaknesses to attackers, and are available to the Treasury multisig owners on request. - **Bot hosting.** The bot currently runs on a contributor-managed server with automatic restart and a health watchdog. It will migrate to 1inch-managed infrastructure once stable. Because the bot is advisory, an outage degrades to today’s manual process rather than causing harm. - **Defense in depth.** This playbook hardens the first layer of protection. The DAO’s existing backstops, Kleros arbitration available to anyone and the 7-of-12 Treasury veto during the 72-hour Timelock, remain unchanged and are not weakened by this proposal. - **Residual risks.** Kleros fees and outcomes are outside the DAO’s control; the 0.5 ETH reserve covers one arbitration at the currently documented rate and may need revision if Kleros parameters change. The 2-of-3 signer set is small by design; if a signer becomes unavailable long-term, the authors will propose a replacement on the forum and the change takes effect only on a passing Snapshot vote. Signer changes on a DAO-funded Safe are not made by the signers themselves, consistent with the prohibition on owner-executed signer changes adopted for the DAO Treasury Safe. ### Governance - **Cost to Treasury:** a one-time 2.5 ETH transfer held as recoverable float. No ongoing spend, no compensation, and no payment to any third party. The signers are existing 1inch contributors acting without remuneration under this proposal. - **Revenue impact:** neutral to slightly positive. Forfeited attacker bonds from won games are returned to the Treasury annually. - **Voting process, staking, tokenomics:** unaffected. - **Reversibility:** the DAO can retire the playbook by a subsequent vote at any time, at which point the full balance is returned. - **Relationship to the Security Council.** 1IP-106 constitutes the DAO Treasury signer set as the 1inch DAO Security Council, whose mandate includes vetoing malicious or faulty payloads during the 72-hour Timelock and emergency response to protect treasury assets. That is the same threat surface this playbook addresses. This proposal does not create a competing body: the Defense Safe operates at the Reality.eth bonding layer before finalization, the Security Council retains the 7-of-12 veto during the Timelock, and neither displaces the other. If the DAO later assigns Reality.eth defense to the Security Council or to a scoped veto role, this playbook is retired under the wind-down provision above. - **Signer protection.** The three signers commit DAO funds under time pressure on the DAO’s behalf. The good-faith safe harbor adopted for the Security Council signers applies to them on the same terms: a signer who in good faith posts, declines to post, or escalates a bond under these decision rules incurs no personal liability to the DAO or token holders for losses that later result, with the same carve-outs for fraud, deliberate misconduct, and knowing breach of this playbook. Without this, the proposal asks contributors to take a personal risk the DAO has already agreed not to impose on its other signers.