From 4a6496a90ba6c0beb7c6ac78525f6cfb5850db1f Mon Sep 17 00:00:00 2001 From: Luke Parker Date: Tue, 12 Mar 2024 00:59:51 -0400 Subject: [PATCH] Add slightly nicer formatting re: Protocol Changes doc --- docs/protocol_changes/index.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/protocol_changes/index.md b/docs/protocol_changes/index.md index 692a0084..263e2cd7 100644 --- a/docs/protocol_changes/index.md +++ b/docs/protocol_changes/index.md @@ -4,6 +4,8 @@ layout: default nav_order: 5 --- +# Protocol Changes + The protocol has no central authority nor organization nor actors (such as liquidity providers/validators) who can compel new protocol rules. The Serai protocol is as-written with all granted functionality and declared rules @@ -11,7 +13,7 @@ present. Validators are explicitly granted the ability to signal for two things to occur: -1) Halt another validator set. +### 1) Halt another validator set. This will presumably occur if another validator set turns malicious and is the expected incident response in order to apply an economic penalty of ideally @@ -22,7 +24,7 @@ validator sets have accepted responsibility, and accepting responsibility requires `Batch` publication). This effectively burns the malicious validators' stake. -2) Retire the protocol. +### 2) Retire the protocol. A supermajority of validators may favor a signal (an opaque 32-byte ID). A common signal gaining sufficient favor will cause the protocol to stop producing