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

v1.17: [zk-token-proof] include VerifyBatchRangeProofU256 in the enable_zk_transfer_with_fee feature gate (backport of #34747) #34765

Merged
merged 1 commit into from
Jan 12, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Jan 12, 2024

This is an automatic backport of pull request #34747 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

…k_transfer_with_fee` feature gate (#34747)

include `VerifyBatchRangeProofU256` in the `enable_zk_transfer_with_fee` feature

(cherry picked from commit bc13642)
Copy link

codecov bot commented Jan 12, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (07acb46) 81.7% compared to head (6c62a68) 81.6%.

Additional details and impacted files
@@            Coverage Diff            @@
##            v1.17   #34765     +/-   ##
=========================================
- Coverage    81.7%    81.6%   -0.1%     
=========================================
  Files         805      805             
  Lines      218796   218798      +2     
=========================================
- Hits       178762   178748     -14     
- Misses      40034    40050     +16     

Copy link
Contributor

@joncinque joncinque left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this logic was missed in #34103, it makes sense to backport. Approving

@samkim-crypto samkim-crypto merged commit 0aea75a into v1.17 Jan 12, 2024
33 checks passed
@samkim-crypto samkim-crypto deleted the mergify/bp/v1.17/pr-34747 branch January 12, 2024 14:28
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.

2 participants