Skip to content
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.

Sign up for GitHub

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

REP-33: transition to Review #46

Merged
merged 10 commits into from
Oct 16, 2024
Merged

REP-33: transition to Review #46

Show file tree
Hide file tree
Changes from 3 commits
Commits
Show all changes
10 commits
Select commit Hold shift + click to select a range
d45b6af
feat: transition to Final
brucexc Oct 9, 2024
15b4857
Merge branch 'main' into REP-33-Final
brucexc Oct 10, 2024
7aaa6b4
chore: simplify the sentence
brucexc Oct 10, 2024
94a0ad8
chore: restore rep-43
brucexc Oct 10, 2024
cc25ca8
chore: grammatical issue
brucexc Oct 10, 2024
4c58af1
chore: grammar issues
brucexc Oct 11, 2024
f1ad86d
fix: update chart
brucexc Oct 14, 2024
ecf0ef9
Merge branch 'main' into REP-33-Final
brucexc Oct 15, 2024
fd5954d
fix: merge conflict
brucexc Oct 15, 2024
996d0c0
Merge branch 'main' into REP-33-Final
brucexc Oct 16, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 10 additions & 11 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,17 +6,16 @@ REP stands for RSS3 Evolution Proposal, a detailed documentation proposed by the

This repository tracks all REPs proposed by the RSS3 Community.

| REP Number | Title | Proposer(s) | Type | Status |
| -------------------------- | ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | --------- |
| [REP-1](./REPs/REP-1.md) | Purpose and Guidelines | <[email protected]> | Process | Living |
| [REP-11](./REPs/REP-11.md) | Protocol Upgrade | [BruceXC](mailto:[email protected]), [HenryQW](mailto:[email protected]), [KallyDev](mailto:[email protected]), [Nya Candy](mailto:[email protected]), [polebug](mailto:[email protected]), [pseudoyu](mailto:[email protected]), [Thomas](mailto:[email protected]) | Protocol | Final |
| [REP-16](./REPs/REP-16.md) | Staking Rewards Taxation Adjustment | [Albert](mailto:[email protected]), [HenryQW](mailto:[email protected]) | Core | Final |
| [REP-20](./REPs/REP-20.md) | Data Availability Layer Integration | [Albert](mailto:[email protected]), [HenryQW](mailto:[email protected]) | Core | Final |
| [REP-26](./REPs/REP-26.md) | Chip Mechanism Upgrade | [BruceXC](mailto:[email protected]) | Core | Candidate |
| [REP-33](./REPs/REP-33.md) | Node State Transition | [KallyDev](mailto:[email protected]), [BruceXC](mailto:[email protected]) | Core | Draft |
| [REP-38](./REPs/REP-38.md) | Demotion and Slashing Mechanism | [Polebug](mailto:[email protected]) | Core | Draft |
| [REP-40](./REPs/REP-40.md) | Whitepaper Updates | [pseudoyu](mailto:[email protected]) | Core | Review |
| [REP-43](./REPs/REP-43.md) | Introducing Payment Processor for Request Fees | [Nya Candy](mailto:[email protected]) | Core | Review |
brucexc marked this conversation as resolved.
Show resolved Hide resolved
| REP Number | Title | Proposer(s) | Type | Status |
| -------------------------- | ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------ |
| [REP-1](./REPs/REP-1.md) | Purpose and Guidelines | <[email protected]> | Process | Living |
| [REP-11](./REPs/REP-11.md) | Protocol Upgrade | [BruceXC](mailto:[email protected]), [HenryQW](mailto:[email protected]), [KallyDev](mailto:[email protected]), [Nya Candy](mailto:[email protected]), [polebug](mailto:[email protected]), [pseudoyu](mailto:[email protected]), [Thomas](mailto:[email protected]) | Protocol | Final |
| [REP-16](./REPs/REP-16.md) | Staking Rewards Taxation Adjustment | [Albert](mailto:[email protected]), [HenryQW](mailto:[email protected]) | Core | Final |
| [REP-20](./REPs/REP-20.md) | Data Availability Layer Integration | [Albert](mailto:[email protected]), [HenryQW](mailto:[email protected]) | Core | Final |
| [REP-26](./REPs/REP-26.md) | Chip Mechanism Upgrade | [BruceXC](mailto:[email protected]) | Core | Final |
| [REP-33](./REPs/REP-33.md) | Node State Transition | [KallyDev](mailto:[email protected]), [BruceXC](mailto:[email protected]) | Core | Final |
| [REP-38](./REPs/REP-38.md) | Demotion and Slashing Mechanism | [Polebug](mailto:[email protected]) | Core | Draft |
| [REP-40](./REPs/REP-40.md) | Whitepaper Updates | [pseudoyu](mailto:[email protected]) | Core | Draft |

## License

Expand Down
52 changes: 31 additions & 21 deletions REPs/REP-33.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
```
REP: REP-33
Title: Node State Transition
Status: Draft
brucexc marked this conversation as resolved.
Show resolved Hide resolved
Status: Final
Type: Core
Created: 19 Jul 2024
Author(s): KallyDev <[email protected]>
Author(s): KallyDev <[email protected]>, BruceXC <[email protected]>
Description: This REP outlines every potential Node state and the transitions between them.
Discussions: https://forum.rss3.io/t/proposal-on-node-state-transition/173
```
Expand All @@ -17,6 +17,7 @@ Discussions: https://forum.rss3.io/t/proposal-on-node-state-transition/173
- [Motivation](#motivation)
- [Specification](#specification)
- [Node State Transition Path](#node-state-transition-path)
- [Reward Mechanism](#reward-mechanism)
- [Rationale](#rationale)

## Abstract
Expand All @@ -32,31 +33,40 @@ Clear definitions and guidelines will support the Network's current functionalit

## Specification

A Node can be in 1 of the following 7 states:
A Node can exist in one of the following 10 states:

1. **Registered**: The Node is registered on the VSL with a sufficient deposit.
2. **Initializing**: The Node is operating on the DSL. Automated tasks will be executed at this stage to ensure the Node is in a healthy condition. This state applies to the initial startup or the first startup following any change in the Node’s coverage.
3. **Online**: The Node is operational and actively participating in network activities on the DSL.
4. **Offline**: The Node is not operational and not participating in network activities on the DSL.
5. **Exiting**: The Node is in the process of exiting the Network on the VSL.
6. **Exited**: The Node has successfully exited the Network on the VSL.
7. **Slashed**: The Node has been slashed due to a violation of network rules or malicious behavior on the VSL.
1. **None**: The initial state of a Node.
2. **Registered**: The Node has been registered on the VSL with a sufficient deposit.
3. **Initializing**: The Node is operating on the DSL. Automated tasks will be executed at this stage to ensure the Node is in a healthy condition. This state applies to the
initial startup or the first startup following any change in the Node’s coverage.
4. **Outdated**: The Node's version does not meet the minimum requirement.
5. **Online**: The Node is operational and actively participating in network activities.
6. **Offline**: The Node is non-operational and not participating in network activities.
7. **Exiting**: The Node is in the process of exiting the Network.
8. **Exited**: The Node has successfully exited the Network.
9. **Slashing**: The Node is about to be penalized for violating network rules or engaging in malicious behavior. It has a 3-epoch appeal period.
10. **Slashed**: The Node has been penalized due to a violation of network rules or malicious behavior.

### Node State Transition Path

![Node State Transition Path](REP-33/node-state-transition-path.png)

1. **Registered** → **Initializing** → **Online**: Node's lifecycle begins in the `None` state. Upon registration, a Node transitions to `Registered`. `Initializing` is the state when the Node is started. After the automatic initialization is completed, it enters `Online` state.
2. **Registered** → (after 30 Epochs) → **Exited**: A `Registered` Node transitions to `Exited` state after 30 Epochs of inactivity.
3. **Online** → (current Epoch) → **Exiting**: An `Online` Node transitions to `Exiting` state upon announcing its intention to exit.
4. **Exiting** → (next Epoch) → **Exited**: An `Exiting` Node transitions to `Exited` state in the next epoch.
5. **Exiting** → **Slashed**: An `Exiting` Node transitions to `Slashed` state if it prematurely exits during the current epoch.
6. **Online** → (current Epoch) → **Offline**: An `Online` Node transitions to `Offline` state immediately within the same epoch if its heartbeat fails.
7. **Online** → (current Epoch) → **Slashed**: An `Online` Node transitions to `Slashed` state immediately within the same epoch if it is slashed.
8. **Slashed** → (next Epoch) → **Online**: A `Slashed` Node transitions to `Online` state in the next epoch if the Operator manually re-online it by the end of the current epoch.
9. **Offline** → (next Epoch) → **Online**: An `Offline` Node transitions to `Online` state in the next epoch if the Operator manually re-online it by the end of the current epoch.
10. **Offline** →(after 30 Epochs) → **Exited**: An `Offline` Node transitions to `Exited` state after 30 Epochs of inactivity.
11. **Exited** → (anytime) → **Registered**: An `Exited` Node can re-register at any time.
1. **None** → **Registered**: A `None` Node transitions to `Registered` state upon meeting the minimum deposit requirement.
2. **Registered** → **Initializing**: Upon registration, a Node transitions to `Registered`. `Initializing` is the state when the Node has started and is indexing data, but has not yet completed the process.
3. **Registered** → **Outdated**: A `Registered` Node transitions to `Outdated` state when the Node is started and its version does not meet the minimum requirement.
4. **Registered**, **Outdated**, **Initializing**, **Slashed** → (anytime) → **Exited**: When a Node is in any of the `Registered`, `Outdated`, `Initializing`, or `Slashed` states, if the operator chooses to exit, the Node immediately enters the `Exited` state.
5. **Initializing** → (next Epoch) → **Online**: After the automatic initialization is completed, it enters `Online` state at the next epoch.
6. **Online** → (current Epoch) → **Exiting**: An `Online` Node transitions to `Exiting` state upon announcing its intention to exit.
7. **Exiting** → (waiting period) → **Exited**: An `Exiting` Node transitions to `Exited` state after completing the waiting period.
8. **Online**, **Exiting** → **Slashing**: An `Online` or `Exiting` Node transitions to `Slashing` state if its demotion count reaches the threshold. The operator can appeal within 3 epochs.
9. **Online**, **Exiting** → (current Epoch) → **Offline**: An `Online` or `Exiting` Node transitions to `Offline` state immediately within the same epoch if the Node is detected to be unavailable.
10. **Offline**, **Slashed** → (current Epoch) → **Initializing**: An `Offline` or `Slashed` Node transitions to `Initializing` state if the Operator manually brings it back online.
11. **Slashing** → (after 3 epochs) → **Slashed**: A `Slashing` Node transitions to `Slashed` state after 3 epochs.
12. **Exited** → (anytime) → **Registered**: An `Exited` Node can re-register at any time.

### Reward Mechanism

Nodes in `Online`, `Initializing`, or `Exiting` states can provide services and receive rewards. Other states are ineligible.

## Rationale

Expand Down
Binary file modified REPs/REP-33/node-state-transition-path.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.