Skip to content

Conversation

acolytec3
Copy link
Contributor

While working on #4021, I discovered that the stateManagerInterface has an optional method verifyVerklePostState that is called verifyPostState on the two verkle state manager implementations.

This cleans up that discrepancy

Copy link

codecov bot commented Apr 24, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.54%. Comparing base (846fea7) to head (daefdfb).
Report is 1 commits behind head on master.

Additional details and impacted files

Impacted file tree graph

Flag Coverage Δ
block 84.33% <ø> (ø)
blockchain 89.32% <ø> (ø)
client 67.99% <ø> (ø)
common 97.51% <ø> (ø)
devp2p 86.78% <ø> (ø)
evm 73.02% <ø> (ø)
mpt 89.69% <ø> (-0.06%) ⬇️
statemanager 69.06% <100.00%> (ø)
static 99.11% <ø> (ø)
tx 90.59% <ø> (ø)
util 89.36% <ø> (ø)
vm 55.50% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@ScottyPoi ScottyPoi force-pushed the fix-verkle-statemanager-API-discrepancy branch from 8898b05 to daefdfb Compare April 24, 2025 23:38
@acolytec3 acolytec3 merged commit 6a2ccd6 into master Apr 25, 2025
40 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants