From 94d902d3226f0844d122e2f62c515cc6b927ffa3 Mon Sep 17 00:00:00 2001 From: Henry Date: Thu, 24 Oct 2024 10:32:07 +0100 Subject: [PATCH] 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