-
Notifications
You must be signed in to change notification settings - Fork 45
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
adding CSM info to group quickstart #426
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -149,11 +149,8 @@ For Step 2, select the "Creator" tab if you are coordinating the creation of the | |
You will use the Launchpad to create an invitation, and share it with | ||
the operators. | ||
<br /> | ||
This video shows the flow within the{" "} | ||
<a href="/docs/dvl/intro#dv-launchpad-links" target="_blank"> | ||
DV Launchpad | ||
</a> | ||
: | ||
This video shows the flow within the {" "} | ||
<a href="/docs/dvl/intro#dv-launchpad-links" target="_blank">DV Launchpad:</a> | ||
</p> | ||
<p align="center"> | ||
<iframe | ||
|
@@ -192,11 +189,30 @@ For Step 2, select the "Creator" tab if you are coordinating the creation of the | |
be functioning for the validator(s) to stay active. | ||
</li> | ||
</ul> | ||
:::info | ||
If you are configuring a cluster for use within Lido's Community Stake Module (CSM), | ||
in the following steps you need to: | ||
<ul> | ||
<li> | ||
Set the <code>validators</code> field to 1. (only 1 CSM Validator can be deployed per cluster via the launchpad). | ||
</li> | ||
<li> | ||
Set the <code>withdrawal configuration</code> to <code>custom</code>. | ||
</li> | ||
<li> | ||
Set <code>withdrawal address</code> to Lido’s Withdrawal Vault Address: 0xF0179dEC45a37423EAD4FaD5fCb136197872EAd9 per [Lido’s documentation](https://docs.lido.fi/deployed-contracts/holesky/). | ||
</li> | ||
<li> | ||
Set the <code>fee recipient</code> to Lido’s Execution Layer Rewards Vault Address: 0xE73a3602b99f1f913e72F8bdcBC235e206794Ac8 per Lido’s [documentation](https://docs.lido.fi/deployed-contracts/holesky/). | ||
</li> | ||
</ul> | ||
::: | ||
<li> | ||
Input the Ethereum addresses for each operator that you collected | ||
previously. If you will be taking part as an operator, click the | ||
"Use My Address" button for Operator 1. | ||
</li> | ||
|
||
<ul> | ||
<li> | ||
Select the desired amount of validators (32 ETH each) the | ||
|
@@ -209,7 +225,7 @@ For Step 2, select the "Creator" tab if you are coordinating the creation of the | |
the "What is your charon client's ENR?" field. | ||
</li> | ||
<li> | ||
Enter the <code>Principal address</code> which should receive | ||
Enter the <code>Withdrawal Address</code> which should receive | ||
the principal 32 ETH and the accrued consensus layer rewards | ||
when the validator is exited. This can optionally be set to the | ||
contract address of a multisig / splitter contract. | ||
|
@@ -261,6 +277,21 @@ For Step 2, select the "Creator" tab if you are coordinating the creation of the | |
<p> | ||
You will use the CLI to create the cluster definition file, which you | ||
will distribute it to the operators manually. | ||
:::info | ||
If you are configuring a cluster for use within Lido's Community Stake Module (CSM), | ||
in the following steps you need to: | ||
<ul> | ||
<li> | ||
Set <code>num-validators=1</code>. (only 1 CSM Validator can be deployed per cluster via the launchpad). | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is the CLI section, not sure this is needed |
||
</li> | ||
<li> | ||
Set <code>fee-recipient-address="0xE73a3602b99f1f913e72F8bdcBC235e206794Ac8"</code>. This is Lido’s Execution Layer Rewards Vault Address, per the Lido [documentation](https://docs.lido.fi/deployed-contracts/holesky/). | ||
</li> | ||
<li> | ||
Set <code>withdrawal-addresses="0xF0179dEC45a37423EAD4FaD5fCb136197872EAd9"</code>. This is Lido’s Withdrawal Vault Address, per the Lido [documentation](https://docs.lido.fi/deployed-contracts/holesky/). | ||
</li> | ||
</ul> | ||
::: | ||
<ol> | ||
<li> | ||
The leader or creator of the cluster will prepare the | ||
|
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think showing holesky addresses here is a bad idea, I don't believe this guide is network specific anywhere other than this.