Dragan Rakita
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
      • Invitee
    • Publish Note

      Publish Note

      Everyone on the web can find and read all notes of this public team.
      Once published, notes can be searched and viewed by anyone online.
      See published notes
      Please check the box to agree to the Community Guidelines.
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Versions and GitHub Sync Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
Invitee
Publish Note

Publish Note

Everyone on the web can find and read all notes of this public team.
Once published, notes can be searched and viewed by anyone online.
See published notes
Please check the box to agree to the Community Guidelines.
Engagement control
Commenting
Permission
Disabled Forbidden Owners Signed-in users Everyone
Enable
Permission
  • Forbidden
  • Owners
  • Signed-in users
  • Everyone
Suggest edit
Permission
Disabled Forbidden Owners Signed-in users Everyone
Enable
Permission
  • Forbidden
  • Owners
  • Signed-in users
Emoji Reply
Enable
Import from Dropbox Google Drive Gist Clipboard
   owned this note    owned this note      
Published Linked with GitHub
1
Subscribed
  • Any changes
    Be notified of any changes
  • Mention me
    Be notified of mention me
  • Unsubscribe
Subscribe
I am thrilled that this milestone has been reached! [Revm](https://github.com/bluealloy/revm) is one of the leading EVMs in the Ethereum ecosystem. Many major projects and companies depend on it, and the number is growing, especially since the development of Reth. Revm has solidified its position as a foundational component of the Ethereum ecosystem, and its significance continues to rise. It is used by clients, block builders, tooling, and many searchers and hobbyists. Revm's stability has been stellar and its execution consistent, leading to heavy reliance on it. Its speed and flexibility make it highly desirable for integration. With `no_std` support, it fits nicely in the zkVM world, where Rust is predominantly used. There are many requirements that Revm fulfills. There was already a lot of confidence in its consensus correctness, and bugs were squashed, which helped develop the client [Reth](https://reth.rs) on top of it. We wanted to increase that confidence even further and have more assurance. The next step for this was an audit. [Guido Vranken](https://guidovranken.com/), a top Ethereum [bug hunter](https://bounty.ethereum.org), was hired to stress test Revm. With his expertise in fuzzing and finding consensus bugs, it has been a pleasure to have him on board. Despite its already extensive usage, Guido managed to find a few undiscovered consensus issues and created a tool for fuzzing that we can reuse. When we discussed how to conduct the audit, the idea of involving others arose: "If there are multiple parties who rely on Revm, then it may make sense to have them co-fund it."" So we did exactly that and made this audit community-driven and sponsored by six companies that use Revm in various ways. * **Paradigm** Foundry, which Paradigm created, was started in the same month as Revm. After some time, the Foundry team switched to Revm, making it the first big project to use it. They were the first to see the potential and are a major reason for Revm's popularity today. More than a year later, an idea was born to build Reth as there was already a working EVM. This is when I finally joined Paradigm, as I enjoyed working on client code. I am really grateful to Georgios and Paradigm for their support and for later hiring me to work on Reth and continue working on Revm. The Reth team is amazing, and it is my privilege to work with them! * **Ethereum Foundation** We wouldn’t be here without Ethereum, so it made sense to include the Ethereum Foundation. After the audit of Revm and Reth is finished, Reth is scheduled to be included in the EF Bug Bounty along with its dependencies, so any bugs found within Revm that has an impact on the Ethereum network will be receiving rewards through the [Ethereum Foundation Bug Bounty Program](https://bounty.ethereum.org). * **Optimism** The Optimism stack and their team are amazing! Revm has support for Optimism changes, which made me think about the future of Revm and support for other EVM chains. The RetroPGF mechanism is a great way to incentivize builders to build even more. * **Nomic Foundation** he builders of Hardhat recently enabled their EDR (Ethereum Development Runtime) framework, which uses Revm at its core. They recognized Revm's potential and started transitioning to it years ago. * **Risc0** Risc0 launched Zeth, their zkEVM system, which is leveraging Revm for execution. It is an awesome company that uses RISC-V for universal zk execution. * **Taiko** At one of the conferences, they approached me about Revm audit efforts and offered to help, so when the list was made, they were included. They care about the lower stack and are one of the first projects to make the [1% Pledge](https://x.com/taikoxyz/status/1755609928167981330?lang=en) for [Protocol Guild](https://protocol-guild.readthedocs.io/en/latest/index.html). I appreciate their support. There are many more projects that depend on Revm, and I am glad that this is the case, as it means the library is doing something good. This is a huge milestone for Revm and me. When I started the project, I didn't imagine it would have such an impact on Ethereum. I appreciate the community, as without it, this would not be possible. I am committed to fulfilling the expectations and obligations of the users who depend on it. The work continues. The future is primarily focused on two things: 1. The next hard fork that includes EOF (EVM Object Format) 2. Revm endgame, but that is a topic for another post.

Import from clipboard

Paste your webpage below. It will be converted to Markdown.

Advanced permission required

Your current role can only read. Ask the system administrator to acquire write and comment permission.

This team is disabled

Sorry, this team is disabled. You can't edit this note.

This note is locked

Sorry, only owner can edit this note.

Reach the limit

Sorry, you've reached the max length this note can be.
Please reduce the content or divide it to more notes, thank you!

Import from Gist

Import from Snippet

or

Export to Snippet

Are you sure?

Do you really want to delete this note?
All users will lose their connection.

Create a note from template

Create a note from template

Oops...
This template is not available.
Upgrade
All
  • All
  • Team
No template found.

Create custom template

Upgrade

Delete template

Do you really want to delete this template?
Turn this template into a regular note and keep its content, versions, and comments.

This page need refresh

You have an incompatible client version.
Refresh to update.
New version available!
See releases notes here
Refresh to enjoy new features.
Your user state has changed.
Refresh to load new user state.

Sign in

Forgot password

or

By clicking below, you agree to our terms of service.

Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
Wallet ( )
Connect another wallet

New to HackMD? Sign up

Help

  • English
  • 中文
  • Français
  • Deutsch
  • 日本語
  • Español
  • Català
  • Ελληνικά
  • Português
  • italiano
  • Türkçe
  • Русский
  • Nederlands
  • hrvatski jezik
  • język polski
  • Українська
  • हिन्दी
  • svenska
  • Esperanto
  • dansk

Documents

Help & Tutorial

How to use Book mode

How to use Slide mode

API Docs

Edit in VSCode

Install browser extension

Get in Touch

Feedback

Discord

Send us email

Resources

Releases

Pricing

Blog

Policy

Terms

Privacy

Cheatsheet

Syntax Example Reference
# Header Header 基本排版
- Unordered List
  • Unordered List
1. Ordered List
  1. Ordered List
- [ ] Todo List
  • Todo List
> Blockquote
Blockquote
**Bold font** Bold font
*Italics font* Italics font
~~Strikethrough~~ Strikethrough
19^th^ 19th
H~2~O H2O
++Inserted text++ Inserted text
==Marked text== Marked text
[link text](https:// "title") Link
![image alt](https:// "title") Image
`Code` Code 在筆記中貼入程式碼
```javascript
var i = 0;
```
var i = 0;
:smile: :smile: Emoji list
{%youtube youtube_id %} Externals
$L^aT_eX$ LaTeX
:::info
This is a alert area.
:::

This is a alert area.

Versions and GitHub Sync
Get Full History Access

  • Edit version name
  • Delete

revision author avatar     named on  

More Less

No updates to save
Compare
    Choose a version
    No search result
    Version not found
Sign in to link this note to GitHub
Learn more
This note is not linked with GitHub
 

Feedback

Submission failed, please try again

Thanks for your support.

On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

Please give us some advice and help us improve HackMD.

 

Thanks for your feedback

Remove version name

Do you want to remove this version name and description?

Transfer ownership

Transfer to
    Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

      Link with GitHub

      Please authorize HackMD on GitHub
      • Please sign in to GitHub and install the HackMD app on your GitHub repo.
      • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
      Learn more  Sign in to GitHub

      Push the note to GitHub Push to GitHub Pull a file from GitHub

        Authorize again
       

      Choose which file to push to

      Select repo
      Refresh Authorize more repos
      Select branch
      Select file
      Select branch
      Choose version(s) to push
      • Save a new version and push
      • Choose from existing versions
      Include title and tags
      Available push count

      Pull from GitHub

       
      File from GitHub
      File from HackMD

      GitHub Link Settings

      File linked

      Linked by
      File path
      Last synced branch
      Available push count

      Danger Zone

      Unlink
      You will no longer receive notification when GitHub file changes after unlink.

      Syncing

      Push failed

      Push successfully