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

docs(protocol): reorganise protocol section #560

Merged
merged 22 commits into from
Mar 11, 2024
Merged

Conversation

idea404
Copy link
Contributor

@idea404 idea404 commented Mar 8, 2024

Reorganises the docs "protocol" section, expanding it across the sidebar and adds some sections

task: https://app.asana.com/0/0/1206696792863505/f

Copy link

github-actions bot commented Mar 8, 2024

Docs preview complete 🚀 see it here: https://omni-dao1ftu4y-omni-engineering.vercel.app

@idea404 idea404 requested a review from ttarsi March 8, 2024 13:49
@idea404 idea404 added the docs Improvements or additions to documentation label Mar 8, 2024
@idea404 idea404 marked this pull request as ready for review March 8, 2024 13:49
@idea404
Copy link
Contributor Author

idea404 commented Mar 8, 2024

This will require re-indexing the site
Also, the content will require another revision as there have been updates (such as refactors) to some of the mentioned portions

Copy link
Contributor

@ttarsi ttarsi left a comment

Choose a reason for hiding this comment

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

awesome, comprehensive, great work 🙌

@ttarsi
Copy link
Contributor

ttarsi commented Mar 8, 2024

awesome, comprehensive, great work 🙌

EVM Equivalence section:

  • Let's change this – make it more about how Omni validators are running exactly the same EVM code as L1 validators. So developers need to make zero changes to their smart contracts or worry about opcode compatibility issues. All developer tooling that works on L1 works with the Omni EVM. Often, EVM chains will be "EVM compatible" but they will have small differences in how the EVM works that developers need to be aware of, they won't support all opcodes, and/or won't include the latest EVM upgrades. Since omni validators run an unmodified EVM client, developers don't need to think about any of these problems on the Omni evm.

Copy link

Docs preview complete 🚀 see it here: https://omni-928jz6njq-omni-engineering.vercel.app

Copy link

Docs preview complete 🚀 see it here: https://omni-65uf8d30r-omni-engineering.vercel.app

Copy link

Docs preview complete 🚀 see it here: https://omni-38nu7e2tp-omni-engineering.vercel.app

Copy link

Docs preview complete 🚀 see it here: https://omni-cs4strlw8-omni-engineering.vercel.app

@idea404 idea404 enabled auto-merge (squash) March 11, 2024 12:35
@idea404 idea404 merged commit d17cce1 into main Mar 11, 2024
8 checks passed
@idea404 idea404 deleted the idea404/docs-protocol branch March 11, 2024 12:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants