Merge pull request #1975 from input-output-hk/djo/1925/update_docs

docs: update since signers now compute what to sign independently
input-output-hk · Oct 4, 2024 · 390e545 · 390e545
2 parents d8e4eff + 255d899
commit 390e545
Show file tree

Hide file tree

Showing 4 changed files with 3 additions and 8 deletions.
diff --git a/docs/website/root/mithril/mithril-network/aggregator.md b/docs/website/root/mithril/mithril-network/aggregator.md
@@ -23,11 +23,9 @@ A **Mithril aggregator** is a trustless node responsible for coordinating the ac
 
 The primary objective of the Mithril aggregator is to coordinate and synchronize the production of Mithril multi-signatures:
 
-- When a new snapshot is ready to be produced (and certified), the Mithril aggregator generates and broadcasts a fresh **beacon** to inform Mithril signers of the specific time reference to employ in computing the message (or digest) for signing
+- It is responsible for broadcasting the **verification keys** (Mithril public keys) of all the registered Mithril signers
 
-- It is also responsible for advertising the **verification keys** (Mithril public keys) of all the registered Mithril signers
-
-- The beacon, the current protocol parameters, and the available verification keys are compiled and shared in a **pending certificate**
+- The current protocol parameters and the available verification keys are compiled and shared in an **epoch settings** data
 
 - Mithril signers can register with it to participate in the signature process later on.
 

diff --git a/docs/website/root/mithril/mithril-network/images/signer-runtime.jpg b/docs/website/root/mithril/mithril-network/images/signer-runtime.jpg
diff --git a/docs/website/root/mithril/mithril-network/signer.md b/docs/website/root/mithril/mithril-network/signer.md
@@ -40,7 +40,6 @@ Ultimately, any signer will have the potential to function as a Mithril aggregat
 
 The Mithril signer establishes a connection with the Mithril aggregator for the following purposes:
 
-- Determining when to sign a new snapshot (via the advertised beacon of the pending certificate)
 - Obtaining the presently used protocol parameters
 - Registering its verification keys (public keys)
 - Receiving the verification keys of all other declared signers, available for the upcoming message signing

diff --git a/docs/website/root/mithril/threat-model.md b/docs/website/root/mithril/threat-model.md
@@ -52,9 +52,7 @@ All Mithril signers and Mithril clients connect to a single aggregator using HTT
 
 Registering a Mithril signing key means that a signer sends its corresponding verification key to the aggregator, for the purpose of distribution to all other Mithril signers.
 
-A Mithril aggregator coordinates creation of signatures by all registered signers. Mithril signers do ask the aggregator whether a signature is pending on a regular basis. The aggregator responds with information what to sign and a list of public information about all registered signers.
-
-Each Mithril signer verifies the information, produces a signature of the requested information to sign and submits that to the aggregator (which verifies the signature being correct upon receiving).
+Each Mithril signer checks if there is something that can be signed independently, produces a signature of what's needed to sign and submits that to the aggregator (which verifies the signature being correct upon receiving).
 
 The aggregator repeatedly checks whether enough valid signatures (to reach the quorum) are available to aggregate a Mithril stake-based multi-signature into a certificate.