From 411b079423352ec28ace590d29b77d7b59bdd34f Mon Sep 17 00:00:00 2001 From: polebug Date: Tue, 30 Jul 2024 14:45:45 +0800 Subject: [PATCH 1/3] REP-38: transition to Review --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 3fa7da8..b1ed7d2 100644 --- a/README.md +++ b/README.md @@ -14,7 +14,7 @@ This repository tracks all REPs proposed by the RSS3 Community. | [REP-20](./REPs/REP-20.md) | Data Availability Layer Integration | [Albert](mailto:iavl@proton.me), [HenryQW](mailto:hi@henry.wang) | Core | Final | | [REP-26](./REPs/REP-26.md) | Chip Mechanism Upgrade | [BruceXC](mailto:xichang1510@gmail.com) | Core | Candidate | | [REP-33](./REPs/REP-33.md) | Node State Transition | [KallyDev](mailto:kallydev@rss3.io) | Core | Draft | -| [REP-38](./REPs/REP-38.md) | Demotion and Slashing Mechanism | [Polebug](mailto:polebug@rss3.io) | Core | Draft | +| [REP-38](./REPs/REP-38.md) | Demotion and Slashing Mechanism | [Polebug](mailto:polebug@rss3.io) | Core | Review | ## License From 46ffc2d46ed03dc7a87015d5883e69f3bbc33049 Mon Sep 17 00:00:00 2001 From: Henry Date: Thu, 24 Oct 2024 10:27:45 +0100 Subject: [PATCH 2/3] fix: merging error --- REPs/REP-38.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/REPs/REP-38.md b/REPs/REP-38.md index f8cf9eb..0b7012d 100644 --- a/REPs/REP-38.md +++ b/REPs/REP-38.md @@ -1,7 +1,7 @@ ``` REP: REP-38 Title: Demotion and Slashing Mechanism -Status: Draft +Status: Review Type: Core Created: 23 Jul 2024 Author(s): polebug @@ -58,7 +58,7 @@ An Enforcer is introduced as a component of GIs in this proposal, it manages dem And here is a figure to assist in the understanding of cross-validation. `-1` leads to a demotion. -![3 responses \[r1,r2,r3\].png](REP-38%2F3%20responses%20%5Br1%2Cr2%2Cr3%5D.png) +![3 responses [r1,r2,r3].png](REP-38%2F3%20responses%20%5Br1%2Cr2%2Cr3%5D.png) # **Rationale** From 94d902d3226f0844d122e2f62c515cc6b927ffa3 Mon Sep 17 00:00:00 2001 From: Henry Date: Thu, 24 Oct 2024 10:32:07 +0100 Subject: [PATCH 3/3] chore: minor updates --- REPs/REP-38.md | 4 ++-- .../{3 responses [r1,r2,r3].png => 3-responses.png} | Bin ... Mainnet Diagrams (1).png => epoch-workflow.png} | Bin 3 files changed, 2 insertions(+), 2 deletions(-) rename REPs/REP-38/{3 responses [r1,r2,r3].png => 3-responses.png} (100%) rename REPs/REP-38/{RSS3 Mainnet Diagrams (1).png => epoch-workflow.png} (100%) diff --git a/REPs/REP-38.md b/REPs/REP-38.md index 0b7012d..dd33b8b 100644 --- a/REPs/REP-38.md +++ b/REPs/REP-38.md @@ -54,11 +54,11 @@ An Enforcer is introduced as a component of GIs in this proposal, it manages dem Here is a figure showing what happens during an Epoch. The figure might be helpful for illustrating the Enforcer’s logic regarding slashing. -![RSS3 Mainnet Diagrams (1).png](REP-38%2FRSS3%20Mainnet%20Diagrams%20%281%29.png) +![Epoch workflow](REP-38/epoch-workflow.png) And here is a figure to assist in the understanding of cross-validation. `-1` leads to a demotion. -![3 responses [r1,r2,r3].png](REP-38%2F3%20responses%20%5Br1%2Cr2%2Cr3%5D.png) +![3 responses](REP-38/3-responses.png) # **Rationale** diff --git a/REPs/REP-38/3 responses [r1,r2,r3].png b/REPs/REP-38/3-responses.png similarity index 100% rename from REPs/REP-38/3 responses [r1,r2,r3].png rename to REPs/REP-38/3-responses.png diff --git a/REPs/REP-38/RSS3 Mainnet Diagrams (1).png b/REPs/REP-38/epoch-workflow.png similarity index 100% rename from REPs/REP-38/RSS3 Mainnet Diagrams (1).png rename to REPs/REP-38/epoch-workflow.png