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

zcash_client_sqlite: Ensure that all shielded change outputs are correctly flagged. #1585

Merged
merged 5 commits into from
Oct 25, 2024

Conversation

nuttycom
Copy link
Contributor

@nuttycom nuttycom commented Oct 23, 2024

Fixes #1571

@nuttycom nuttycom force-pushed the debug/is_shielding branch 3 times, most recently from cacbf26 to 0d82e1e Compare October 23, 2024 16:48
@nuttycom nuttycom changed the title zcash_client_sqlite: Once a note is determined to be change, don't rescind that determination. zcash_client_sqlite: Ensure that all shielded change outputs are correctly flagged. Oct 23, 2024
Copy link

codecov bot commented Oct 23, 2024

Codecov Report

Attention: Patch coverage is 91.83673% with 4 lines in your changes missing coverage. Please review.

Project coverage is 56.48%. Comparing base (01552bd) to head (d753090).
Report is 6 commits behind head on main.

Files with missing lines Patch % Lines
.../wallet/init/migrations/fix_bad_change_flagging.rs 80.95% 4 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1585      +/-   ##
==========================================
+ Coverage   56.39%   56.48%   +0.08%     
==========================================
  Files         149      150       +1     
  Lines       19078    19126      +48     
==========================================
+ Hits        10759    10803      +44     
- Misses       8319     8323       +4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor

@str4d str4d left a comment

Choose a reason for hiding this comment

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

Reviewed 0d82e1e

…ash#1571

The update to a shielding transaction causes the information that the
output is considered change to be lost. This happens because the
scanning process does not have access to any information about the
inputs to the transaction, and so it does not recognize the output as
change.
…scind that determination.

This is a minimal and correct but incomplete fix for
zcash#1571. Additional work to distinguish change outputs
is necessary to update existing wallets that have made an incorrect
change determination in the past.
@nuttycom nuttycom force-pushed the debug/is_shielding branch 3 times, most recently from bca02d5 to d753090 Compare October 24, 2024 23:03
@nuttycom
Copy link
Contributor Author

nuttycom commented Oct 24, 2024

force-pushed to address review comments then

force-pushed to rebase on main.

Copy link
Contributor

@str4d str4d left a comment

Choose a reason for hiding this comment

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

utACK d753090

@str4d str4d merged commit 6d6959f into zcash:main Oct 25, 2024
52 checks passed
Copy link
Contributor

@daira daira left a comment

Choose a reason for hiding this comment

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

Post-hoc ACK

@nuttycom nuttycom deleted the debug/is_shielding branch October 25, 2024 03:30
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.

Bug in is_shielding state going from TRUE to FALSE after the first confirmation
3 participants