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
In the process of using Besu, I found that the get_Proof interface returned an Account Not Found error when processing non existent accounts.
This seems to be inconsistent with the provisions of EIP-1186:
Proofs for non existent values
In case an address or storage-value does not exist, the proof needs to provide enough data to verify this fact. This means the client needs to follow the path from the root node and deliver until the last matching node. If the last matching node is a branch, the proof value in the node must be an empty one. In case of leaf-type, it must be pointing to a different relative-path in order to proof that the requested path does not exist.
I would like to know why Besu returns an error directly and what are the considerations for this design.
In addition, are there any plans to modify the implementation of the get_Proof interface for non existent accounts in the future?
If you see it, please answer my confusion, thank you very much~
The text was updated successfully, but these errors were encountered:
In the process of using Besu, I found that the get_Proof interface returned an Account Not Found error when processing non existent accounts.
This seems to be inconsistent with the provisions of EIP-1186:
I would like to know why Besu returns an error directly and what are the considerations for this design.
In addition, are there any plans to modify the implementation of the get_Proof interface for non existent accounts in the future?
If you see it, please answer my confusion, thank you very much~
The text was updated successfully, but these errors were encountered: