You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many of the errors we encountered on the CPU side where invalid final tries (usually the state trie). We currently print to the logs the tries computed by the CPU upon kernel failure, though this isn't really helpful on its own.
We already have a tool (eth-trie-tools) to highlight trie discrepancies between two (expected) identical tries which happened to have at least one diff point, but the process is slow and tedious. Ideally, we would like to have an automated tool that:
keeps the initial / final tries generated by the decoder for a given payload (we normally hash the final tries)
look for a diff between tries
for discrepancies in txn or receipt tries, display the distinct, decoded payloads
for discrepancies in the state trie:
highlight the account that's different
look for the associated address
if the issue lies in the storage root, find the discrepancy in the account's storage trie
This will be particularly helpful when we start working on actual blocks with SMT.
The text was updated successfully, but these errors were encountered:
Many of the errors we encountered on the CPU side where invalid final tries (usually the state trie). We currently print to the logs the tries computed by the CPU upon kernel failure, though this isn't really helpful on its own.
We already have a tool (
eth-trie-tools
) to highlight trie discrepancies between two (expected) identical tries which happened to have at least one diff point, but the process is slow and tedious. Ideally, we would like to have an automated tool that:txn
orreceipt
tries, display the distinct, decoded payloadsThis will be particularly helpful when we start working on actual blocks with SMT.
The text was updated successfully, but these errors were encountered: