Skip to content

Conversation

@owen-eth
Copy link
Contributor

Describe your changes

Initial registry for Lido V3 Staking Vaults
-No staking/slashing, only freezing
-Operator must be whitelisted
-Operator specifies their vault and keys to register
-Specified Vault's node operator must match the msg.sender, Vault must also be indexed within Lido's Vault Hub
-Lido V3 is not on mainnet yet, this is just for Hoodi test usage

Potential future design:
-Lido Staking Vaults accept ETH and mint steth to users, we can have our registry accept steth so to allow slashing on our side.

Issue ticket number and link

Fixes # (issue)

Checklist before requesting a review

  • I have added tests that prove my fix is effective or that my feature works
  • I have made corresponding changes to the documentation

@owen-eth owen-eth requested a review from shaspitz August 21, 2025 00:16
@owen-eth owen-eth changed the title Lido registry hoodi Feat: Lido registry hoodi Aug 21, 2025
@owen-eth owen-eth changed the title Feat: Lido registry hoodi feat: Lido registry hoodi Aug 21, 2025
@owen-eth owen-eth changed the title feat: Lido registry hoodi feat: lido v3 registry hoodi Aug 21, 2025
Copy link
Contributor

@shaspitz shaspitz left a comment

Choose a reason for hiding this comment

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

General flow looks good 👍

// ---- Constants ----
uint256 private constant BLS_PUBKEY_LEN = 48;

// ---- Events ----
Copy link
Contributor

Choose a reason for hiding this comment

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

We can put all these events and errors in an ILidoV3Middleware.sol file

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