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

Add bold integration article #1413

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

Add bold integration article #1413

wants to merge 8 commits into from

Conversation

anegg0
Copy link
Contributor

@anegg0 anegg0 commented Jul 3, 2024

This PR adds @leeederek's article about BoLD adoption by Orbit chains' owners.

Currently reviewed by @leeederek

Copy link

vercel bot commented Jul 3, 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 12, 2024 1:36pm

@cla-bot cla-bot bot added the s label Jul 3, 2024
@anegg0 anegg0 requested a review from leeederek July 3, 2024 03:28
@anegg0 anegg0 self-assigned this Jul 3, 2024
@anegg0 anegg0 marked this pull request as ready for review July 3, 2024 03:28

Adopting <a data-quicklook-from="bold">Arbitrum BoLD</a> brings new security benefits to Orbit chains that are independent of whether or not validation is permissionless. These new security benefits include improved resistance to delay attacks and increased censorship resistance for `L3s`. Because of these new security benefits, we strongly recommend teams to upgrade their Orbit chains to use Arbitrum BoLD (for the security benefits) but **keep validation permissioned**. Below is a quick breakdown of the impacts of permissioned BoLD vs. permissionless BoLD on your Orbit chain:

| Permissioned BoLD | Permissionless BoLD |
Copy link
Member

Choose a reason for hiding this comment

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

Is there a better way to present this? The first row in the 2nd column is basically saying "everything on the left, plus ..."

Intent here is to show the audience that Permissionless BoLD has the same benefits at Permissioned BoLD but many other caveats, risks, and nuances to consider.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I modified the permissioned/permissionless trade-off tables.
The format I'm proposing would only be relevant if we have solid arguments to fill in the blanks. If we don't, we could remove the table and mention the trade-offs in the text, as you did in the previous version.

lmk what you think :)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@leeederek , can you confirm?

anegg0 and others added 2 commits July 3, 2024 09:45
…s.mdx

Co-authored-by: Derek <103802618+leeederek@users.noreply.github.com>
…s.mdx

Co-authored-by: Derek <103802618+leeederek@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants