Skip to content

feat: add edf to docs - #962

Open
chasingrainbows wants to merge 1 commit into
mainfrom
feat/edf-docs
Open

feat: add edf to docs#962
chasingrainbows wants to merge 1 commit into
mainfrom
feat/edf-docs

Conversation

@chasingrainbows

Copy link
Copy Markdown
Contributor

Please, go through these steps before you request a review:

📝 Describe your changes

  1. EDF manual added
  2. EDF security policy added

🔎 Attach a source of truth or evidence that allows reviewers to confirm the changes independently

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds new Execution Delegation Framework (EDF) operator documentation to the guides section, covering setup, key custody requirements, and rotation/incident procedures.

Changes:

  • Adds an “Execution Delegation Framework” category to the Guides sidebar.
  • Introduces an EDF Operator Guide covering multisig setup, DelegationContract deployment/verification, monitoring, and Oracle/Council daemon configuration.
  • Adds EDF rotation/incident runbook and a draft operator key-custody policy.

Reviewed changes

Copilot reviewed 4 out of 14 changed files in this pull request and generated 3 comments.

File Description
sidebars.js Adds an EDF guides category and links the new EDF docs into navigation.
docs/guides/edf/edf-operator-guide.md New end-to-end operator setup guide for EDF (multisig, deployment, monitoring, daemon config).
docs/guides/edf/edf-rotation-and-incidents.md New runbook for routine rotations and emergency revocation/termination.
docs/guides/edf/key-custody-policy-for-edf-operators.md New draft key custody policy for EDF owner/delegate keys, rotation cadence, and incident response.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.


**Applies to:** Operators of permissioned roles behind an EDF `DelegationContract`

**Maintained:** On the Lido research forum; may be revised without a protocol change
Target: **within 30 minutes** of detection. Hard limit: **4 hours**.

It takes effect immediately and cancels any rotation in flight.
2. **Notify** the Lido security contact — Telegram **@Vorobushek2004** and **@chasingrainbow** — and

2. **Notify security and operators.**

Notify the Lido contributors’ security contact — Telegram **@Vorobushek2004** and **@chasingrainbow** — and the operators’ coordination channel as soon as the revocation transaction is sent. Include:
| Network | `DelegationFactory` address |
| --- | --- |
| Ethereum mainnet | _TBD — will be published before the migration_ |
| Hoodi | [`0x84Ba66ad82E7C6edf11Db8143B17c263Ec19CeD5`](https://hoodi.etherscan.io/address/0x84Ba66ad82E7C6edf11Db8143B17c263Ec19CeD5#code) |

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.


| Variable | Value |
| --- | --- |
| `DELEGATION_CONTRACT_ADDRESS` | Your `DelegationContract` address. Config validation **fails at startup** if it is empty or not a valid address — even while the DSM is still on v3/v4. |

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

v4 only; support for v3 has been removed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants