From ebb5d5424478d3339987fea1728da34b1ae543f5 Mon Sep 17 00:00:00 2001 From: Theguyhere0 <52550799+Theguyhere0@users.noreply.github.com> Date: Mon, 8 Feb 2021 11:19:57 -0800 Subject: [PATCH] Fixed typos in the Reputation Mining section - Deleted an extra article in front of "challenge-response" in section 5.4, "verifying a submission" - Corrected the spelling of "accounts" in section 5.9 --- src/network/mining.tex | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/network/mining.tex b/src/network/mining.tex index e3b9439..3217b15 100644 --- a/src/network/mining.tex +++ b/src/network/mining.tex @@ -143,7 +143,7 @@ \subsubsection*{Who can submit a new root hash?} \subsubsection*{Verifying a submission} If only one state is submitted by the end of the submission period, then the new state is accepted, and proposals of the next state can begin to be made. This is expected to be the most common occurrence. -If more than one state has been submitted, then either someone has made a mistake, or there is a malicious entity trying to introduce a fraudulent reputation change. In this event, the a challenge-response protocol can establish which state is incorrect (see Section \ref{sec:challenge-response}). +If more than one state has been submitted, then either someone has made a mistake, or there is a malicious entity trying to introduce a fraudulent reputation change. In this event, the challenge-response protocol can establish which state is incorrect (see Section \ref{sec:challenge-response}). \subsubsection*{Mining rewards} @@ -404,4 +404,4 @@ \subsection{Costs and rewards of mining}\label{subsec:mining-costs-and-rewards} \subsection{Emergency shutdown}\label{sec:big-red-button} -Section \ref{sec:escape-hatches} described a transaction from a whitelisted account can put a colony into `recovery mode' during which the state can be edited, the effects of bugs can be corrected and upgrades can be made. Similarly, the reputation mining process will also have an emergency stop-and-repair mechanism (to begin with). This will allow the whitelisted accountes to revert the reputation root hash to a previous version and halt all updates to the reputation state until the issues have been resolved (which will likely involve a contract upgrade). The colonies will be able to continue operations as usual using the reputations of the last valid state, which will be temporarily frozen and not decay. +Section \ref{sec:escape-hatches} described a transaction from a whitelisted account can put a colony into `recovery mode' during which the state can be edited, the effects of bugs can be corrected and upgrades can be made. Similarly, the reputation mining process will also have an emergency stop-and-repair mechanism (to begin with). This will allow the whitelisted accounts to revert the reputation root hash to a previous version and halt all updates to the reputation state until the issues have been resolved (which will likely involve a contract upgrade). The colonies will be able to continue operations as usual using the reputations of the last valid state, which will be temporarily frozen and not decay.