(v5) Processing of internalized "leaf nodes" in the storage tries #165
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
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cerc-io/go-ethereum#165
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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?
In order to create their own eth.storage_cids entry that associates them with a "leaf_key" and links by CID and mh_key to the parent branch node they are internalized within.
Same issue as in https://github.com/vulcanize/issue_tracking/issues/5 but in addition to a post-processing fix we can apply on historical data we need to fix this issue during statediff processing going forward. This will be significantly more involved and requires some additional exploration into how to best handle this. At a high level this will require modifying the trie.Iterator/DifferenceIterator and our statediff.Builder.
Note that the same approach can and should be done to improve our fix for the logTrie, so that the entries in log_cids reference the encapsulating branch node and not just a dangling log IPLD.
Related (this is the proper fix of the underlying issue in) https://github.com/cerc-io/ipld-eth-server/issues/120