-
Notifications
You must be signed in to change notification settings - Fork 6
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
f56e4dc
commit 56e2ee4
Showing
3 changed files
with
53 additions
and
1 deletion.
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 |
---|---|---|
@@ -1,2 +1,12 @@ | ||
# Shared Validator Network | ||
# Node Operators | ||
|
||
Node operators can be an individual or organization that have the set up required to opt-into the distributed systems across the Solayer network. Node operators are delegated with the restaked LST or native staked SOL to perform operations, and in return to be rewarded, or slashed if there is misbehavior.  | ||
|
||
|
||
|
||
Solayer is approaching the node operator design in two categories: **general-purpose**, **sidecar-specific**. This is to efficiently:  | ||
|
||
1. efficiently scale the network by distributing the workload  | ||
2. categorize responsibilities between general-purpose and sidecar-specific node operator | ||
3. avoid patterns of long-tail sidecars and node operators  | ||
4. optimized for specific tasks, such as transaction sequencing to improve performance  |
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 |
---|---|---|
@@ -1,2 +1,27 @@ | ||
# General Purpose Node Operator | ||
|
||
General Purpose Node Operators play a crucial role in maintaining the security and integrity of the Solana blockchain. They are responsible for finalizing blocks, validating transactions, and participating in the consensus mechanism. | ||
|
||
|
||
|
||
### Type  | ||
|
||
1. Must be a full node in the Solana validator set  | ||
|
||
### High level responsibilities:  | ||
|
||
1. **Block Validation and Finalization**: | ||
* Validate the correctness of transactions and blocks on Solana. | ||
* Finalize blocks, ensuring they are added to the blockchain in a secure and orderly manner. | ||
* Collaborate with other validators to reach consensus and maintain the chain's integrity. | ||
2. **State Commitment Handling**: | ||
* Receive state commitments from sidecar-specific node operators. | ||
* Incorporate these state commitments into the blockchain to finalize transactions that originated from sidecars. | ||
* Validate for sidecar state accuracy and integrity. | ||
3. **Consensus Participation**: | ||
* Actively participate in the Solana consensus mechanism (Proof of History and Tower BFT). | ||
* Propose and vote on blocks as part of the consensus process. | ||
* Work collaboratively with other validators to achieve network-wide consensus. | ||
|
||
|
||
|
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 |
---|---|---|
@@ -1,2 +1,19 @@ | ||
# SVN-Specific Node Operator | ||
|
||
Sidecar-Specific Node Operators are superset of validators dedicated to specific sidecars, through nominated or random consensus algorithms. Their primary role is to manage sidecar operations, which involve collecting and sequencing transactions specific to a designated sidecar, and providing state commitments to General Purpose Node Operators for finalization. | ||
|
||
**Type** | ||
|
||
* Can operate as light nodes within the Solana validator set. | ||
|
||
**Key Responsibilities** | ||
|
||
1. **Transaction Collection and Sequencing**: | ||
* Collect transactions that are designated for the sidecar to which the operator is assigned. | ||
* Sequence the transactions in an orderly and efficient manner, ensuring that they are ready for inclusion in the Solana blockchain. | ||
2. **State Commitment Provision**: | ||
* Generate state commitments for the sequenced transactions. | ||
* Provide these state commitments to General Purpose Node Operators, enabling them to finalize the transactions on the Solana blockchain. | ||
3. **Sidecar Maintenance**: | ||
* Ensure the smooth operation of the sidecar, including monitoring its performance and handling any issues that arise. | ||
* Keep the sidecar software updated and in sync with the Solana network.\ |