Skip to content

fix: use expected_is_private instead of hardcoded true in empty-root path#31

Open
drappi-ai wants to merge 2 commits intozellic-audit-feb-2026from
cdai__fix-209-hardcoded-private
Open

fix: use expected_is_private instead of hardcoded true in empty-root path#31
drappi-ai wants to merge 2 commits intozellic-audit-feb-2026from
cdai__fix-209-hardcoded-private

Conversation

@drappi-ai
Copy link

Summary

  • verify_proof's empty-root fast path hardcoded expected_private: true in the ValueMismatch error instead of using the caller-provided expected_is_private
  • One-line fix: expected_private: trueexpected_private: expected_is_private

Addresses SeismicSystems/internal#209.

Test plan

  • empty_root_value_mismatch_uses_expected_private regression test
  • All existing tests pass

Demonstrates that verify_proof's empty-root fast path hardcodes
expected_private: true instead of using the caller-provided
expected_is_private parameter (issue #209).
…path

In verify_proof's empty-root fast path, the ValueMismatch error was
hardcoding expected_private: true instead of reflecting the caller's
expected_is_private parameter. Fixes SeismicSystems/internal#209.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant