Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

【EIP-1186】Proofs for non existent values #8075

Open
RuiQi857 opened this issue Jan 3, 2025 · 0 comments
Open

【EIP-1186】Proofs for non existent values #8075

RuiQi857 opened this issue Jan 3, 2025 · 0 comments
Labels
bug Something isn't working P2 High (ex: Degrading performance issues, unexpected behavior of core features (DevP2P, syncing, etc))

Comments

@RuiQi857
Copy link

RuiQi857 commented Jan 3, 2025

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~

@RuiQi857 RuiQi857 added the bug Something isn't working label Jan 3, 2025
@macfarla macfarla added the P2 High (ex: Degrading performance issues, unexpected behavior of core features (DevP2P, syncing, etc)) label Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working P2 High (ex: Degrading performance issues, unexpected behavior of core features (DevP2P, syncing, etc))
Projects
None yet
Development

No branches or pull requests

2 participants