Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DAO Ops unit name fixed #554

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

DAO Ops unit name fixed #554

wants to merge 2 commits into from

Conversation

kate-aleksseeva
Copy link
Contributor

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

📝 Describe your changes

  1. DAO Ops unit name fixed

@kate-aleksseeva kate-aleksseeva requested a review from a team as a code owner March 13, 2025 17:14
@@ -1,6 +1,6 @@
# Verifying address ownership for Lido DAO ops
Copy link
Contributor

Choose a reason for hiding this comment

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

operational multisigs


Using EOA across Lido DAO ops or protocol contracts requires providing a public "proof of ownership". Main use-cases here are using address as a signer in Lido DAO ops multisigs or using EOAs for offchain tooling where specific rights might be required.
Copy link
Contributor

Choose a reason for hiding this comment

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

operational multisigs
operational

@@ -13,7 +13,7 @@ Using EOA across Lido DAO ops or protocol contracts requires providing a public
4. The `sig` field in the result json is the signature hash.
2. Publish the message along with the signature hash on twitter or other easily accessible social media.
3. Share the link to the post as a comment at the relevant [Lido DAO forum](https://research.lido.fi) post.
4. Make sure to follow the [general rules of thumb](/guides/multisig-signer-manual) for being a signer in Lido DAO ops multisigs.
Copy link
Contributor

Choose a reason for hiding this comment

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

operational

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.

None yet

2 participants