Find and replace all _([:alpha:][:alnum:]*) with _{\mathrm{$1}} #515
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
For 87edbc6, I meant "Remove |
Using Libre Open Office with match case and regex.
|
@pirapira, please merge this first to avoid further conflicts that will be time-consuming to resolve. |
…rm{p}} => T_{\mathrm{g}}T_{\mathrm{p}}
|
That makes sense. |
pirapira
suggested changes
Jan 30, 2018
Paper.tex
Outdated
| @@ -116,7 +116,7 @@ \section{The Blockchain Paradigm} \label{ch:overview} | |||
|
|
|||
| Ethereum, taken as a whole, can be viewed as a transaction-based state machine: we begin with a genesis state and incrementally execute transactions to morph it into some final state. It is this final state which we accept as the canonical ``version'' of the world of Ethereum. The state can include such information as account balances, reputations, trust arrangements, data pertaining to information of the physical world; in short, anything that can currently be represented by a computer is admissible. Transactions thus represent a valid arc between two states; the `valid' part is important---there exist far more invalid state changes than valid state changes. Invalid state changes might, \eg, be things such as reducing an account balance without an equal and opposite increase elsewhere. A valid state transition is one which comes about through a transaction. Formally: | |||
| \begin{equation} | |||
| \linkdest{Upsilon_state_transition}\boldsymbol{\sigma}_{t+1} \equiv \Upsilon(\boldsymbol{\sigma}_t, T) | |||
| \linkdest{Upsilon_state_transition}\boldsymbol{\sigma}_{t+1} \equiv \Upsilon(\boldsymbol{\sigma}_{\mathrm{t}}, T) | |||
There was a problem hiding this comment.
t is a variable here. So it should stay italic.
Paper.tex
Outdated
| @@ -127,7 +127,7 @@ \section{The Blockchain Paradigm} \label{ch:overview} | |||
|
|
|||
| Formally, we expand to: | |||
| \begin{eqnarray} | |||
| \boldsymbol{\sigma}_{t+1} & \equiv & \Pi(\boldsymbol{\sigma}_t, B) \\ | |||
| \boldsymbol{\sigma}_{t+1} & \equiv & \Pi(\boldsymbol{\sigma}_{\mathrm{t}}, B) \\ | |||
There was a problem hiding this comment.
Here as well, t is a variable and should stay italic.
|
@pirapira, it's fixed, again, please merge this first. |
|
Oh, I missed your message. I'm fixing the conflicts myself now. |
pirapira
reviewed
Feb 2, 2018
| @@ -210,20 +210,20 @@ \subsection{World State} \label{ch:state} | |||
| The account state comprises the following four fields: | |||
|
|
|||
| \begin{description} | |||
| \item[nonce] \linkdest{account_nonce}A scalar value equal to the number of transactions sent from this address or, in the case of accounts with associated code, the number of contract-creations made by this account. For account of address $a$ in state $\boldsymbol{\sigma}$, this would be formally denoted $\boldsymbol{\sigma}[a]_n$. | |||
There was a problem hiding this comment.
Wait, wait, the change on account_nonce is weird.
pirapira
reviewed
Feb 2, 2018
Paper.tex
Outdated
| \item[mixHash]\linkdest{mixHash_H__m}{} A 256-bit hash which, combined with the nonce, proves that a sufficient amount of computation has been carried out on this block; formally $H_m$. | ||
| \item[nonce]\linkdest{block_nonce_H__n}{} A 64-bit hash which, combined with the mix-hash, proves that a sufficient amount of computation has been carried out on this block; formally $H_n$. | ||
| \item[parentHash]\linkdest{parent_Hash_H__p_def_words}{} The Keccak 256-bit hash of the parent block's header, in its entirety; formally $H_{\mathrm{p}}$. | ||
| \item[ommersHash]\linkdest{beneficiary_H__c}{} The Keccak 256-bit hash of the ommers list portion of this block; formally $H_{\mathrm{o}}$. |
See PR ethereum#515
|
Tested locally. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
... using Libre Open Office with regular expressions ticked.