Add info about DVT setup in operator #52
Open
+44
−0
Conversation
This file contains hidden or 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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds documentation for setting up Distributed Validator Technology (DVT) with the StakeWise operator, explaining the architecture and configuration requirements.
Changes:
- Added documentation of DVT setup components and their responsibilities
- Documented the validator registration procedure for DVT configurations
- Added configuration details for using the public DVT relayer
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| operator-v3/alternative-key-management/dvt/index.mdx | Adds sections describing DVT components and validator registration workflow |
| operator-v3/alternative-key-management/api-mode.mdx | Documents DVT relayer configuration and usage |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| Performs validator duties | ||
|
|
||
| ### Stakewise Operator |
There was a problem hiding this comment.
Corrected capitalization of 'Stakewise' to 'StakeWise' for brand consistency.
Suggested change
| ### Stakewise Operator | |
| ### StakeWise Operator |
| 1. Operator sends a list of public keys from the deposit data to the relayer, then polls the relayers for the exit signature(s) | ||
| 2. Relayer creates VoluntaryExit(s) out of public keys and stores to DB. VoluntaryExits can be received through relayer API. | ||
| 3. DVT sidecars poll VoluntaryExits they can sign from the relayer, create exit signatures for them and post to the relayer. | ||
| 4. Relayer i) receives exit signature shares from the sidecars, ii) Restores exit signature from sidecar shares, verifies exit signature, creates shares for oracles, encrypts with oracle public keys and stores to DB. The encrypted shares for oracles are available through relayer API. |
There was a problem hiding this comment.
This step description is overly long and difficult to parse. Consider breaking it into sub-steps (4a, 4b, 4c) to improve readability: receiving shares, restoring and verifying signatures, and encrypting for oracles.
Suggested change
| 4. Relayer i) receives exit signature shares from the sidecars, ii) Restores exit signature from sidecar shares, verifies exit signature, creates shares for oracles, encrypts with oracle public keys and stores to DB. The encrypted shares for oracles are available through relayer API. | |
| 4. Relayer processes exit signatures: | |
| a. Receives exit signature shares from the sidecars. | |
| b. Restores exit signatures from sidecar shares and verifies the restored signatures. | |
| c. Creates shares for oracles, encrypts them with oracle public keys, and stores them to the DB. The encrypted shares for oracles are available through the relayer API. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.