Skip to content
Permalink
Browse files

Merge pull request #759 from input-output-hk/spec/shelley/typos-issue…

…-749

Issue #749 fix typos
  • Loading branch information...
JaredCorduan committed Aug 13, 2019
2 parents 01f1f22 + 253fcbc commit d96d1ad85a409ed5d2dba1c2d2c68b803d907161
@@ -876,7 +876,7 @@ \subsection{Verifiable Random Function}
\end{itemize}

\begin{figure}
\emph{VRF helper funnction}
\emph{VRF helper function}
\begin{align*}
& \fun{vrfChecks} \in \Seed \to \PoolDistr \to \unitInterval \to \BHBody \to \Bool \\
& \fun{vrfChecks}~\eta_0~\var{pd}~\var{f}~\var{bhb} = \\
@@ -918,7 +918,7 @@ \subsection{Overlay Schedule}
\item A mapping $\var{osched}$ of slots to an optional genesis key.
In the terminology of \cite{delegation_design},
the slots in $\var{osched}$ are the ``OBFT slots''.
A slot in this map with a value of $\Nothing$ is a non-active slots,
A slot in this map with a value of $\Nothing$ is a non-active slot,
otherwise it is an active slot and its value designates the genesis key
responsible for producing the block.
\item The epoch nonce $\eta_0$.
@@ -212,7 +212,8 @@ \subsection{Delegation Transitions}
\item $\var{retiring}$ tracks stake pool retirements, using a map from hashkeys to
the epoch in which it will retire.
\item $\var{cs}$ stores the latest operational certificate issues numbers used for each pool.
The numbers are used the operation certificate transition in Figure~\ref{fig:rules:ocert}.
The numbers are used in the operation certificate transition
in Figure~\ref{fig:rules:ocert}.
\end{itemize}
\end{itemize}

@@ -691,12 +692,12 @@ \subsection{Stake Pool Rules}
\begin{itemize}
\item In the case of a pool retirement certificate, if the pool key is not in
the domain of the stake pools mapping, there is a
\em{StakePoolNotRegisteredOnKey} failure.
{\em StakePoolNotRegisteredOnKey} failure.
\item In the case of a pool retirement certificate, if the retirement epoch is
not between the current epoch and the relative maximal epoch from the current
epoch, there is a \em{StakePoolRetirementWrongEpoch} failure.
epoch, there is a {\em StakePoolRetirementWrongEpoch} failure.
\item If the delegation certificate is not of one of the pool types, there is a
\em{WrongCertificateType} failure.
{\em WrongCertificateType} failure.
\end{itemize}

\clearpage
@@ -875,7 +876,7 @@ \subsection{Delegation and Pool Combined Rules}
The base case triggers the following state transformation:
\begin{itemize}
\item Reward accounts are set to zero for each corresponding withdrawal.
\item The genesis key delegation mapping is updated accourding to the future delegation
\item The genesis key delegation mapping is updated according to the future delegation
mapping. For each genesis key, we take the most recent delegation in $\var{fdms}$
that is past the current slot.
\item The future genesis key delegation has any items past the current slots removed.
@@ -1087,14 +1087,13 @@ \subsection{Rewards Distribution Calculation}
\item $\var{maxP}$, maximum rewards the pool can claim if the pledge is met,
and zero otherwise.
\item $\var{poolR}$, the pool's actual reward, based on its performance.
\item $\var{mRewards}$, the member's rewards as a mapping of reward accouts to coin.
\item $\var{mRewards}$, the member's rewards as a mapping of reward accounts to coin.
\item $\var{lReward}$, the leader's reward as coin.
\item $\var{potentialRewards}$, the combination of $\var{mRewards}$ and $\var{lRewards}$.
\item $\var{rewards}$, the restriction of $\var{potentialRewards}$ to the active
reward accounts.
\end{itemize}
\item The $\fun{reward}$ function applies $\fun{rewardOnePool}$ to each registered stake
pool, calculating both the full reward mapping.
\item The $\fun{reward}$ function applies $\fun{rewardOnePool}$ to each registered stake pool.
\end{itemize}

%%
@@ -1301,7 +1300,7 @@ \subsection{Reward Update Calculation}
\item Add each individual reward to the global reward mapping.
\end{itemize}

These two functions will be used in the blockchain transitions systems in Section~\ref{sec:chain}.
These two functions will be used in the blockchain transition systems in Section~\ref{sec:chain}.
In particular,
$\fun{createRUpd}$ will be used in Equation~\ref{eq:reward-update},
and $\fun{applyRUpd}$ will be used in Equation~\ref{eq:new-epoch}.
@@ -102,7 +102,7 @@ \section{Protocol Parameters}
\fun{activeSlotCoeff},
\fun{d},
\fun{extraEntropy},
\fun{pv},
\fun{pv}
\end{center}
%
\emph{Abstract Functions}

0 comments on commit d96d1ad

Please sign in to comment.
You can’t perform that action at this time.