Document that log_cids entries can contain references to logTrie leaf node IPLDs OR log IPLDs. #120
Labels
No Label
bug
critical
documentation
duplicate
enhancement
Epic
good first issue
help wanted
Integration tests
invalid
question
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/ipld-eth-server#120
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?
Due to work around for https://github.com/vulcanize/go-ethereum/issues/161
You can distinguish the two in two ways:
[2]interface{}{}
(first member the partial path, second the log RLP) for a log trie node and into&types.Log{}
for a logAlso note that the only time a log_cids entry can reference a log IPLD instead of a logTrie leaf node IPLD is if the log doesn't contain any topics and has an empty data field (otherwise it's leaf node will be longer than 32 bytes). But you could have a log without any topics or data that produces a leaf node > 32 bytes in length if the partial path of the node is long enough.
@ashwinphatak drawing your attention to this is as it affects post-processing/data consumption.