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

A custom script for Lido configuration #58

Open
2 tasks
HananINouman opened this issue Sep 15, 2024 · 0 comments
Open
2 tasks

A custom script for Lido configuration #58

HananINouman opened this issue Sep 15, 2024 · 0 comments

Comments

@HananINouman
Copy link
Collaborator

HananINouman commented Sep 15, 2024

🎯 Problem to be solved

We need a lido custom script to create a file for clusters that contains a cluster invite, rewards address (Obol Split Wrapper Reward Address/ObolLidoSplit), splitter address (0xSplit Address/SplitWallet ).

🛠️ Proposed solution

  1. Build a method to create a splitter for Lido cluster operators where ObolRAF is not a recipient, since its the feeRecipient of the ObolLidoSplit with 12.5% split. Will be similar to createObolTotalSplit in our sdk without the ObolRAF split so it can be refactored if put in the sdk. Split should be even for all the cluster operators?

2.Build a method to deploy ObolLidoSplit (The contract that does wrapping from stEth to wstEth cause splitter doesnt support a rebasing token) by calling createSplit from ObolLidoSplitFactory and passing the splitter address.
Holesky and Mainnet addresses for ObolLidoSplitFactory can be find in obol-splits readme.

  1. The script should set the Lido withdrawal vault and Lido Execution Layer Rewards Vault addresses as withdrawal_address/fee_recipient_address in the cluster configuration.
    Holesky and Mainnet addresses can be found here https://operatorportal.lido.fi/modules/community-staking-module
  • For major overhaul of docs, design doc link:

🧪 Tests

  • Netlify deployment build tests passing

👐 Additional acceptance criteria

❌ Out of Scope

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

No branches or pull requests

1 participant