v5 functional updates #339
Labels
No Label
bug
critical
duplicate
enhancement
epic
help wanted
in progress
invalid
low priority
question
rebase
v1
v5
wontfix
Copied from Github
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cerc-io/go-ethereum#339
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "ian/v5_dev"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Will close https://github.com/cerc-io/go-ethereum/issues/196, https://github.com/cerc-io/go-ethereum/issues/165, https://github.com/cerc-io/go-ethereum/issues/236, https://github.com/cerc-io/go-ethereum/issues/266, https://github.com/cerc-io/go-ethereum/issues/277
The main changes in v5 are:
Database changes:
uncle_hash
=>uncles_hash
mh_key
=>cid
state_cids
now only stores leaf nodes, so the PK can useleaf_key
in its tuplestate_accounts
table internalized intostate_cids
since each record corresponds to an account nowstorage_cid
s now only stores leaf nodes, so the PK can useleaf_key
in its tupleleaf_cid
=>cid
inreceipt_cids
andlog_cids
tablesaccess_list_elements
tablepublic.blocks
=>ipld.blocks
Statediff process changes:
ipld.blocks
(we can materialize them on demand if needed, or cache using a "proof watcher")Misc:
TODO:
0438809cb4 (r908033293)
and how we are fixing the internal leaf node issueGoing to do the remaining TODOs in a separate PRs. This one is large enough,
@roysc pinging you just so you are aware of this, no need to review atm.
Merging this, cherry-pick PR otw.