This repository has been archived by the owner on Dec 5, 2021. It is now read-only.
Add community Replicators and Verifiers with instructions #175
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.
Allows community members to run their own Replica and Verifier nodes of the OMGX Rinkeby L2.
A replica node looks at the L2, and is a 1:1 copy of the L2.
A verifier node looks at transactions and the L1, and can be used to generate the data (state roots) that can be used to detect a fraudulent Sequencer. If the Sequencer manipulates transactions, then the state roots it injects into the L1 will be incorrect. That type of fraud can be spotted by looking at the transactions and independently calculating the state roots.
Broad community participation is the bedrock of L2 security, since otherwise, fraud might go undetected.
NOTE: A verifier node is essential, but not sufficient, for fraud-proving and removal of fraudulent transactions.