bluealloy/revm

Implement manual deserialize for AccountInfo

Open

#2,564 opened on Jun 1, 2025

View on GitHub
 (5 comments) (0 reactions) (1 assignee)Rust (1,019 forks)user submission
good first issue

Repository metrics

Stars
 (2,194 stars)
PR merge metrics
 (Avg merge 1d 14h) (32 merged PRs in 30d)

Description

#[cfg_attr(feature = "serde", derive(serde::Serialize, serde::Deserialize))]
pub struct AccountInfo {

matches the non standard eth_getAccountInfo endpoint response:

https://github.com/alloy-rs/alloy/blob/c04ef82f3a63c97cb3332a78b3c18dca47966ad3/crates/rpc-types-eth/src/account.rs#L9-L21

this means for an rpc db this could be replaced with single rpc call if the node supports that endpoint and directly deserialize into revm AccountInfo if deserialize is manually impl so that the codehash is computed during deserde

   let (nonce, balance, code) = tokio::join!(nonce, balance, code,);

TODO

  • add manual deserde that in addition to the current format also supports the eth_getAccountInfo response

Contributor guide

Research direction
Implement a custom Deserialize for AccountInfo that supports both the default serde derive format and the eth getAccountInfo endpoint response format. Ensure codehash is computed during deserialization. See the linked alloy code for response structure.
Tech stack
rust
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Rustserde
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65