Skip to content

Commit

Permalink
fix: correct multiple typos around files (#25)
Browse files Browse the repository at this point in the history
  • Loading branch information
antews authored Dec 9, 2024
1 parent c255474 commit 7795b80
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
4 changes: 2 additions & 2 deletions hub/generalities/gas/constraints.tex
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@

The gas cost of an instruction matters to the present arithmetization \emph{if and only if} it is either unexceptional or raises an \oogxSH{} in the arithmetization.
For exceptional instructions the \zkEvm{} sets the next gas value to $0$.
For (most) unexceptional instructions the next value of gas is (unsurprisingly) obtained by substracting the gas cost from the currently avaialble gas.
For (most) unexceptional instructions the next value of gas is (unsurprisingly) obtained by subtracting the gas cost from the currently available gas.
However, pricing is special for \inst{CALL}-type and \inst{CREATE}-type instructions and we defer to the relevant instruction handling section.
\begin{enumerate}[resume]
\item \If
Expand All @@ -70,6 +70,6 @@
\end{enumerate}
Some details:
(\ref{hub: generalities: gas: resuming execution gas constraint}) asserts that when an execution context reaches its conclusion (as witnessed by $\cn\new_{i} = \caller_{i}$) the $\gasNext$ column on that row must contain the left over gas in the present context.
We are unable to settle the ``call gas'' or ``create gas'' provided to a child context spawned through a \inst{CREATE}-type or \inst{CALL}-type instruction at this level of generatlity, whence the \relevantValue{} in constraint~(\ref{hub: generalities: gas: spawning new context}). It is a complex question and will be settled when we deal with the processing of those instruction families.
We are unable to settle the ``call gas'' or ``create gas'' provided to a child context spawned through a \inst{CREATE}-type or \inst{CALL}-type instruction at this level of generality, whence the \relevantValue{} in constraint~(\ref{hub: generalities: gas: spawning new context}). It is a complex question and will be settled when we deal with the processing of those instruction families.

\issue{Constraint~(\ref{hub: generalities: gas: could blow up}) could blow up if we don't handle precompiles, pure transfers and deployments with empty code correctly.}
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
\begin{center}
\boxed{ \text{The constriants presented below assumes that } \mmuInstFlagRamToRamSansPadding _{i} = 1. }
\boxed{ \text{The constraints presented below assumes that } \mmuInstFlagRamToRamSansPadding _{i} = 1. }
\end{center}
\begin{description}
\item[\underline{Progression:}]
Expand Down

0 comments on commit 7795b80

Please sign in to comment.