Validate proof with verkle

[matkt]

trafficstars

Description

As an [Actor], I want [feature] so that [why].

Acceptance Criteria

• [Criteria 1]

Steps to Reproduce (Bug)

1. [Step 1]
2. [Step 2]
3. [Step ...]

Expected behavior: [What you expect to happen]

Actual behavior: [What actually happens]

Frequency: [What percentage of the time does it occur?]

Logs (if a bug)

Please post relevant logs from Besu (and the consensus client, if running proof of stake) from before and after the issue.

Versions (Add all that apply)

• Software version: [besu --version]
• Java version: [java -version]
• OS Name & Version: [cat /etc/*release]
• Kernel Version: [uname -a]
• Virtual Machine software & version: [vmware -v]
• Docker Version: [docker version]
• Cloud VM, type, size: [Amazon Web Services I3-large]
• Consensus Client & Version if using Proof of Stake: [e.g. Teku, Lighthouse, Prysm, Nimbus, Lodestar]

Smart contract information (If you're reporting an issue arising from deploying or calling a smart contract, please supply related information)

• Solidity version [solc --version]
• Repo with minimal set of deployable/reproducible contract code - please provide a link
• Please include specifics on how you are deploying/calling the contract
• Have you reproduced the issue on other eth clients

Additional Information (Add any of the following or anything else that may be relevant)

• Besu setup info - genesis file, config options
• System info - memory, CPU

[matkt]

link to the PRs

https://github.com/hyperledger/besu-native/pull/169 https://github.com/hyperledger/besu-verkle-trie/pull/61

[matkt]

can I link this ticket to you ? @thomas-quadratic

[thomas-quadratic]

Definitely thanks, will look at it next week

[matkt]

we stopped to work on this one as the cryptographic part of verkle will maybe change in the future

[github-actions[bot]]

This issue is stale because it has been open for 6 months with no activity.