Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bold edits technical deep dive #1213

Open
wants to merge 74 commits into
base: master
Choose a base branch
from
Open

Conversation

anegg0
Copy link
Contributor

@anegg0 anegg0 commented Apr 22, 2024

PR Goal: editing the converted GFMD version of the "Technical deep dive" article.

@anegg0 anegg0 self-assigned this Apr 22, 2024
@cla-bot cla-bot bot added the s label Apr 22, 2024
@anegg0 anegg0 requested a review from leeederek April 22, 2024 20:59
Copy link

vercel bot commented Apr 22, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
arbitrum-docs ✅ Ready (Inspect) Visit Preview Jul 3, 2024 7:29pm

@anegg0 anegg0 closed this Apr 22, 2024
@anegg0 anegg0 deleted the Bold-edits-technical-deep-dive branch April 22, 2024 21:09
@anegg0 anegg0 restored the Bold-edits-technical-deep-dive branch April 22, 2024 21:09
@anegg0 anegg0 reopened this Apr 22, 2024
Co-authored-by: Derek <103802618+leeederek@users.noreply.github.com>
Co-authored-by: Derek <103802618+leeederek@users.noreply.github.com>
anegg0 and others added 2 commits June 20, 2024 10:30
Co-authored-by: Derek <103802618+leeederek@users.noreply.github.com>
Co-authored-by: Derek <103802618+leeederek@users.noreply.github.com>
Co-authored-by: Derek <103802618+leeederek@users.noreply.github.com>
Copy link
Contributor Author

@anegg0 anegg0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm!

arbitrum-docs/bold/concepts/bold-technical-deep-dive.md Outdated Show resolved Hide resolved
arbitrum-docs/bold/concepts/bold-technical-deep-dive.md Outdated Show resolved Hide resolved
- **Fraud proofs:** Proofs of a single step of `WAVM` execution of Arbitrum's state transition function, which are submitted to Ethereum and verified in the `EVM` via a smart contract. These proofs allow Ethereum to be the final arbiter of disagreements over assertions in the rollup contracts, which cannot be falsified by any parties as there is only a single, correct result of executing a `WASM` instruction on a pre-state.
- **Challenge protocol:** A set of rules through which a disagreement on an assertion is resolved using Ethereum as the final arbiter. Ethereum's VM can verify one-step proofs of deterministic computation that can confirm a challenge winner in Arbitrum's rollup contracts.
- **Bonding of funds:** Creating an assertion in the rollup contracts requires the submitter to join the validator set by putting up a large bond in the form of `WETH`. Subsequent assertions posted by the same party do not require more bonds. Instead, the protocol always considers validators to be bonded to their latest posted assertion. The bonded funds are taken away if another competing assertion is confirmed. In the case of confirming an assertion, the associated bonded funds can be withdrawn.
- **Honest validator:** An entity that knows the correct state of the Arbitrum L2 chain and will participate in confirming assertions and challenging invalid assertions if they exist.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note that there are different flavors of validators. By default, all Arbitrum Nitro nodes are "watchtower" validators meaning they will detect invalid assertions and log warnings to the user, but not participate in challenges. You don't need any money for bonding if you run a watchtower validator

anegg0 and others added 2 commits July 3, 2024 12:26
Co-authored-by: Raul Jordan <raul@prysmaticlabs.com>
Co-authored-by: Raul Jordan <raul@prysmaticlabs.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants