cerc-io/ipld-eth-statedb
16
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity
Geth StateDB that works ontop of ipld-eth-db, leveraging its unique indexes
34 Commits 1 Branch 10 Tags 1 MiB
Go 100%
31aec61d7e
Go to file
i-norden 31aec61d7e fix for difficult to identify bug due to block_num arg being overriden by optimistic get_storage_at path which then can mess up the pessimistic path in very particular scenarios
2023-03-08 16:44:49 -06:00
internal add unit tests 2023-03-05 16:45:18 +08:00
.gitignore init commit 2023-02-22 18:57:42 -06:00
access_list.go port over required internal geth packages 2023-02-23 16:10:34 -06:00
config.go fix pgx dep; go.mod 2023-03-01 14:06:40 -06:00
database.go update to use get_storage_at functions 2023-03-07 20:41:53 -06:00
go.mod add unit tests 2023-03-05 16:45:18 +08:00
go.sum add unit tests 2023-03-05 16:45:18 +08:00
journal.go remove snapshot usage and unused internal methods; note this is different than the journaling used to simulate state transitions 2023-02-28 12:08:06 -06:00
README.md update readme 2023-03-01 22:36:17 -06:00
sql.go update to use get_storage_at functions 2023-03-07 20:41:53 -06:00
state_object.go removeu unused method hash arg 2023-03-06 11:46:07 -06:00
statedb_test.go fix for difficult to identify bug due to block_num arg being overriden by optimistic get_storage_at path which then can mess up the pessimistic path in very particular scenarios 2023-03-08 16:44:49 -06:00
statedb.go fixes 2023-03-05 16:31:01 +08:00

README.md

ipld-eth-statedb

Implementation of the geth vm.StateDB on top of ipld-eth-db, to allow us to plug into existing EVM functionality. Analogous to ipfs-ethdb but at one database abstraction level higher. This allows us to bypass the trie-traversal access pattern normally used by the EVM (and which ipfs-ethdb allows us to replicate ontop of our Postgres IPLD blockstore in the "public.blocks" table) and access state and storage directly in the "state_cids" and "storage_cids" tables.

Note: "IPFS" is chosen in the name of "ipfs-ethdb" as it can function through an IPFS BlockService abstraction or directly ontop of an IPLD blockstore, whereas this repository is very tightly coupled to the schema in ipld-eth-db.