Skip to content

docs: add Lido Automation Owner multisig - #1004

Closed
tamtamchik wants to merge 2 commits into
mainfrom
docs/lido-automation-owner-msig
Closed

tamtamchik wants to merge 2 commits into
mainfrom
docs/lido-automation-owner-msig

Conversation

@tamtamchik

@tamtamchik tamtamchik commented Oct 2, 2026 •

Copy link
Copy Markdown
Member

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

📝 Describe your changes

  1. Add section 2.21 Lido Automation Owner Multisig to docs/multisigs/committees.md: address, purpose, 3/5 quorum and the list of signers.
  2. The multisig is technical and does not manage or custody any funds, so there is no forum post or Snapshot vote behind it.

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

  1. Safe setup (owners and 3/5 threshold): https://app.safe.global/settings/setup?safe=eth:0x23AC4BF8ca7345eE533B12705aF40F69060D9b5b
  2. Signer verification for the new addresses:

@tamtamchik
tamtamchik requested a review from a team as a code owner October 2, 2026 08:30
Copilot AI balanced review requested due to automatic review settings October 2, 2026 08:30

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.

Copilot review overview

🟢 Approval recommended

The documentation is consistent with the provided evidence and existing committee format.

Review effort: Balanced
Findings: None

What changed in this PR

Adds documentation for the Lido Automation Owner multisig.

Changes:

  • Documents its purpose, address, and 3/5 quorum.
  • Lists all five signers and verification links.
File Description
docs/​multisigs/​committees.md Adds section 2.21 for the automation multisig.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@tamtamchik
tamtamchik force-pushed the docs/lido-automation-owner-msig branch from 73a7cef to ed17dc1 Compare October 2, 2026 10:27
TheDZhon
TheDZhon previously approved these changes Oct 2, 2026

@TheDZhon TheDZhon 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.

LGTM, though only the Ethereum Safe is linked. Section 2.8.2 already shows the format for one address on several networks.

We should have it for: Ethereum, Arbitrum, Base, Optimism and Linea.

@TheDZhon TheDZhon 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.

GG

@lemonjelly27

Copy link
Copy Markdown
Contributor

Thanks for adding this to the registry!

One thing before approval - the signer verifications don't yet follow the address ownership guide: the signed message should name the handle and the multisig, be posted publicly, and be linked from a forum post. The two out of three new signatures are address-only, and others attest the Safe Harbor Committee multisig, not this one.

I get that the multisig is technical and holds no funds but that explains no Snapshot, but doesn't waive verification IMO. Hence, the verification should keep the name and address bindings independently checkable.

@tamtamchik

Copy link
Copy Markdown
Member Author

Closed per internal discussion.

@tamtamchik tamtamchik closed this Oct 2, 2026
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.

4 participants