updated SSV DKG ceremony#122
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
|
||
| # DKG Ceremony | ||
|
|
||
| In the DKG ceremony the SSV operators generate the validator key shares together. The full private key is never constructed on any machine. The ceremony is run with [`ssv-dkg` ↗](https://github.com/ssvlabs/ssv-dkg) and involves two roles: **operators**, who each run a long-lived `ssv-dkg` service, and an **Initiator**, who triggers the ceremony and collects its outputs (the Initiator does not need to be an operator, though in a self-run cluster it usually is). The full [ceremony flow ↗](https://docs.ssv.network/stakers/tools/ssv-dkg-client/#flow-description) is abstracted away by the [SSV webapp ↗](https://app.ssv.network), which generates the command and the resulting files for you. |
There was a problem hiding this comment.
The ceremony is run with
ssv-dkg↗ and involves two roles: operators, who each run a long-livedssv-dkgservice, and an Initiator, who triggers the ceremony and collects its outputs (the Initiator does not need to be an operator, though in a self-run cluster it usually is).
Long sentences are a bit of a slog here. Mind turning this into a bulleted list?
- operators
- initiator
| -u $(id -u):$(id -g) \ | ||
| --env-file .env \ | ||
| -v $(pwd)/data:/data \ | ||
| europe-west4-docker.pkg.dev/stakewiselabs/public/dvt-operator-sidecar:v2.0.0 |
There was a problem hiding this comment.
Latest version is v2.1.0, released today
| 4. Pull and run the Relayer: | ||
|
|
||
| ```bash | ||
| export DVT_RELAYER_VERSION=v1.0.0 |
There was a problem hiding this comment.
Latest version is v1.1.0 , released today
| :::custom-notes[Public Key] | ||
| Pay close attention to the **pubkey** field in the output, as it contains the public key needed to register the Operator later on the SSV network. | ||
| To extract just the public key value, run: | ||
| The file contains your operator's RSA key pair: the private key, encrypted with your password, which the SSV node uses to decrypt its assigned validator key shares; and the public key `pubkey` in plaintext, which you use to register the operator on SSV. To print the `pubkey`, run: |
There was a problem hiding this comment.
The file contains your operator's RSA key pair: the private key, encrypted with your password, which the SSV node uses to decrypt its assigned validator key shares; and the public key
pubkeyin plaintext, which you use to register the operator on SSV.
Long sentence with enumeration. Format as list?
|
|
||
| 2. Set the values for your SSV operator: | ||
|
|
||
| ```ini |
There was a problem hiding this comment.
Syntax highlight is missing on rendered preview https://docs-367dqii75-stakewise.vercel.app/operator/alternative-key-management/dvt/ssv-dkg.
How to fix: add ini support rohit-gohri/redocusaurus#68
|
|
||
| ## Step 3: Register the Key Shares | ||
|
|
||
| The Initiator registers the key shares on SSV so the encrypted shares are published on-chain, where the Sidecars read each operator's share. **You do not deposit here:** in the StakeWise flow the **Vault** deposits later, once it has accumulated enough assets, through the Relayer (Step 6), not via the SSV Launchpad. |
There was a problem hiding this comment.
SSV Launchpad.
Should be "Ethereum Launchpad"
2 participants
No description provided.