Ssv staking #125
Open
Ssv staking #125
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
Eth Fees Migration
SSV Staking version 1
SSV Staking (Operators + IM)
RaekwonIII
requested review from
Alex-ssvlabs and
taylorferran
as code owners
Modified Subgraph examples to be inline with SSV Staking changes
Essentials draft
arielssv
reviewed
Jan 26, 2026
Contributor
arielssv
left a comment
arielssv
left a comment
There was a problem hiding this comment.
comments until operator docs
| ### Overview | ||
|
|
||
| If you're new to ssv network, go through [the Learn section](/learn/introduction/) to understand its core concepts first. | ||
| Bulk registration flow is roughly outlined in the schema above. |
Contributor
There was a problem hiding this comment.
this guide needs a better description e.g. "This quickstart guide outlines how to generate validator keys, split them to key shares and register them to the SSV network on the Hoodi testnet using the SSV-SDK throughout the following steps" (this is just a quick draft example, you do not have to use this)
| - Lastly, you can start experimenting by interacting with [our Hoodi Testnet](/developers/testnet) smart contracts, before interacting [with the Mainnet ones](/developers/smart-contracts/README.md). | ||
|
|
||
| ## How to integrate with SSV | ||
| :::note Prerequisite |
Contributor
There was a problem hiding this comment.
I think this should be at the end of the "overview" before the 1st step.
| :::warning | ||
| Development Notice: This SDK is currently under active development and testing. It is not recommended for production use at this time. | ||
|
|
||
| This section and SDK are a work in progress and will be continuously updated as new components of the SDK are released. |
Contributor
There was a problem hiding this comment.
Do we still need this warning?
| | ------------------- | -------- | ---------------------------------------------------- | | ||
| | operatorIds | uint64[] | An array of operator IDs of the cluster. | | ||
| | amount | uint256 | Amount of ETH to deposit to cluster's balance after migration. | | ||
| | cluster | tuple\[] | Object containing the latest cluster snapshot data - obtained using the [SSV Subgraph](../tools/ssv-subgraph/subgraph-examples#cluster-snapshot), or [SSV Scanner](../tools/ssv-scanner) tools If this is the 1st validator within a specific cluster (unique set of operators), use - \{0,0,0,true,0\} | |
Contributor
There was a problem hiding this comment.
remove "If this is the 1st validator within a specific cluster (unique set of operators), use - {0,0,0,true,0}"
| * `ValidatorAdded(address indexed owner, uint64[] operatorIds, bytes publicKey, bytes shares, Cluster cluster)` | ||
|
|
||
| ### **`bulkRegisterValidator(publicKey, operatorIds, shares, amount, cluster)`** | ||
| ### **`bulkRegisterValidator(publicKey, operatorIds, shares, cluster)`** |
Contributor
There was a problem hiding this comment.
we need breaking changes indication here?
| In addition to operator fees, stakers are also required to pay a ‘network fee’ for each validator they run through the network. | ||
|
|
||
| The network fee is a fixed cost determined by the DAO that governs the network. Also denominated in SSV and similar to operator fees, they are paid continuously over time to the DAO treasury. | ||
| The network fee is a fixed cost determined by the DAO that governs the network. It's accessible through the [SSV Network Views smart contract](/developers/smart-contracts/ssvnetworkviews#getnetworkfee-) or via the [Subgraph](/developers/tools/ssv-subgraph/subgraph-examples#dao-constants-and-protocol-network-fee-index). It is denominated in ETH and SSV token. Similarly to operator fees, they are paid continuously over time to the DAO treasury. |
Contributor
There was a problem hiding this comment.
- theres only ETH
- remove paid continuously over time to DAO treasury
| The network fee is a fixed cost determined by the DAO that governs the network. It's accessible through the [SSV Network Views smart contract](/developers/smart-contracts/ssvnetworkviews#getnetworkfee-) or via the [Subgraph](/developers/tools/ssv-subgraph/subgraph-examples#dao-constants-and-protocol-network-fee-index). It is denominated in ETH and SSV token. Similarly to operator fees, they are paid continuously over time to the DAO treasury. | ||
|
|
||
| This capital is used to fund, grow, and develop activities and projects in the ecosystem that have passed the voting process. | ||
| This capital is used to fund, grow, and develop activities and projects in the ecosystem that have passed the voting process. |
|  | ||
|
|
||
| :::warning Legacy SSV Clusters | ||
| This documentation focuses on **ETH clusters** (the current standard), but the formulas also apply to legacy SSV clusters during the transition period. |
Contributor
There was a problem hiding this comment.
theres only ETH -you can remove this
|
|
||
| Clusters are created when registering validators to the network and are accessible and owned by the wallet address that transmitted the transaction. This means that the address is the cluster's owner, enabling it to manage its balance and its chosen validators/operators. | ||
|
|
||
| :::warning Legacy SSV Clusters |
| Payments are facilitated by maintaining a cluster balance in the SSV network smart contract, which keeps a balance sheet for all clusters. | ||
|
|
||
| Clusters are created when registering validators to the network are accessible and owned by the wallet address that transmitted the transaction. This means that the address is the cluster's owner, enabling it to manage its balance and its chosen validators/operators. | ||
| **Clusters pay fees in native ETH**, providing simpler and more efficient fee payment. |
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.