[NO MERGE] Verkle trees #7890
Closed
[NO MERGE] Verkle trees #7890
+7,535
−1,565
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| import tech.pegasys.teku.spec.config.SpecConfigCapella; | ||
| import tech.pegasys.teku.spec.util.DataStructureUtil; | ||
|
|
||
| class ExecutionWitnessTest { |
Check notice
Code scanning / CodeQL
Unused classes and interfaces
| } | ||
|
|
||
| private <T> Optional<T> randomOptional(final Supplier<T> elementSupplier) { | ||
| return new Random(nextSeed()).nextBoolean() |
Check warning
Code scanning / CodeQL
Random used only once
|
Follow ethereum/consensus-specs#3827 |
|
Code has been pushed to a branch verkle-trees in this repo. Will close the PR for now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Description
Verkle trees implementation.
Experimental feature #6346
As it's not implemented as a feature which could be turned off or on, it shouldn't be merged to the master and kept in branch until it's scheduled for some fork. After that it could be split in smaller chunks for better PRs
Fixed Issue(s)
Documentation
doc-change-requiredlabel to this PR if updates are required.Changelog