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

Store account info in DB #40

Closed
MegaRedHand opened this issue Jun 14, 2024 · 0 comments · Fixed by #63
Closed

Store account info in DB #40

MegaRedHand opened this issue Jun 14, 2024 · 0 comments · Fixed by #63
Assignees
Labels
storage Issues related to storing blockchain data

Comments

@MegaRedHand
Copy link
Collaborator

The DB table should be keyed by account address, and store the account's nonce, balance, and bytecode hash

@juanbono juanbono added this to the Read-only RPC Node milestone Jun 14, 2024
@mpaulucci mpaulucci added the storage Issues related to storing blockchain data label Jun 18, 2024
@lferrigno lferrigno moved this to Todo in ethrex_l1 Jun 26, 2024
@fmoletta fmoletta moved this from Todo to In Review in ethrex_l1 Jun 26, 2024
@github-project-automation github-project-automation bot moved this from In Review to Done in ethrex_l1 Jun 26, 2024
mpaulucci pushed a commit to mpaulucci/lambda_ethereum_rust that referenced this issue Oct 16, 2024
**Motivation**

 Enable storing account information in DB
 
**Description**
 

* Rename `Account` into `GenesisAccount` and add a separate `Account`
struct containing the storage, code, and info fields, with the info
being an `AccountInfo` struct containing the code hash. Also implement
conversion from `GenesisAccount` to `Account`
* Create `AccountInfos` table mapping addresses to account info
* Implement TODO comment related to encoding

<!-- Link to issues: Resolves lambdaclass#111, Resolves lambdaclass#222 -->

Closes lambdaclass#40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
storage Issues related to storing blockchain data
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

4 participants