> For the complete documentation index, see [llms.txt](https://etherfi.gitbook.io/etherfi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://etherfi.gitbook.io/etherfi/security/security-and-risks/multisigs-and-controls/signing-configuration-changelog.md).

# Signing Configuration Changelog

#### Upgrade path: Upgrade Admin Safe

<table><thead><tr><th width="146.52685546875">Effective (UTC)</th><th>What changed</th><th width="206.9619140625">From → To</th></tr></thead><tbody><tr><td>2026-07-14</td><td><strong>26Q2 security upgrade executed</strong> (10-day timelock batch). Privileged roles consolidated into a single tiered RoleRegistry; Blacklister and RevokeAdmin went live; monitoring-key pauses became time-bounded. Safe signer sets, thresholds, and timelock delays unchanged.</td><td>Roles: ~30 per-contract → <strong>9 tiered (RoleRegistry)</strong></td></tr><tr><td>2026-04-29</td><td>Upgrade hardening<strong>.</strong> Added 3 owners to the Safe and raised threshold; raised Timelock delay.</td><td>Safe<br><strong>4-of-7 → 6-of-10</strong><br><br>Timelock<br><strong>3 days → 10 days</strong></td></tr><tr><td>2024-03-26</td><td>Owner set rebalanced to 7 and threshold raised. This established the steady-state config that held for ~2 years.</td><td>Safe 3-of-6 → <strong>4-of-7</strong></td></tr><tr><td>2024-03-07</td><td>Upgrade Timelock raised to its production delay.</td><td>Timelock 1 day → <strong>3 days</strong></td></tr><tr><td>2024-02-24</td><td><strong>Timelock bootstrap.</strong> Upgrade Timelock deployed with a 1-hour delay, then tuned during setup (1h → 5 min → 1 day) before settling.</td><td>Timelock 0 → 1h → … → 1 day</td></tr><tr><td>2024-02-16</td><td><strong>Safe bootstrap.</strong> Upgrade Admin Safe deployed; initial owner set assembled and rotated during setup.</td><td>Safe deployed <strong>3-of-6</strong>; owner churn, threshold held at 3</td></tr></tbody></table>

#### Operating path: Operating Admin Safe

<table><thead><tr><th width="145.82373046875">Effective (UTC)</th><th width="392.3802490234375">What changed</th><th>From → To</th></tr></thead><tbody><tr><td>2026-04-22</td><td>Added 2 owners and raised threshold</td><td>Safe 3-of-5 → <strong>4-of-7</strong></td></tr><tr><td>2026-04-16</td><td>Operating Timelock raised to its production delay.</td><td>Timelock 8h → <strong>2 days</strong></td></tr><tr><td>2025-03-20</td><td><strong>Operating Timelock deployed.</strong> Day-to-day operations move behind a timelock for the first time (8-hour delay).</td><td>Timelock 0 → <strong>8 hours</strong></td></tr><tr><td>2024-10-08</td><td>Threshold raised.</td><td>Safe 2-of-5 → <strong>3-of-5</strong></td></tr><tr><td>2024-04-19</td><td>Threshold raised above 1 and an owner removed</td><td>Safe 1-of-6 → <strong>2-of-5</strong></td></tr><tr><td>2023-07-14</td><td><strong>Safe bootstrap and early operation.</strong> Operating Admin Safe deployed as 1-of-3; owners added/removed over the following months, threshold held at 1 throughout.</td><td>Safe deployed <strong>1-of-3</strong> → 1-of-6</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://etherfi.gitbook.io/etherfi/security/security-and-risks/multisigs-and-controls/signing-configuration-changelog.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.