paymentId/address discrepancy in ledger_state file - follow up to 2172
See original GitHub issueDescription
Logging as a follow up to https://github.com/brave/brave-browser/issues/2172#issuecomment-456826171 per discussion with @NejcZdovc
We have some users who are in a state where their paymentId/addresses in ledger_state don’t match (the paymentId in ledger_state is not actually associated with the addresses listed) per #1831. We need to fix users who are in this state.
Background/Context for historical purposes: Logged in issue #1831 you’ll see that there was an issue with paymentId and address mismatch after using Restore functionality. This issue was fixed for users going forward, however, we still need to fix users who are already in this mismatched state. That was logged in #2172 as a follow up issue. However, there was some miscommunication where it was thought that the ledger_state file contained the correct addresses, where unfortunately it did not. The fix for 2172 was to have the UI update to reflect what was in ledger_state, but what is in ledger_state is wrong. We need to take an additional step to update the addresses in ledger_state to be the ones that correspond with the paymentId in ledger_state. After this is done, the fix from 2172 should correctly display the addresses in the UI.
Steps to Reproduce
- Install 0.56.6 dmg (this is a Beta version)
- Launch with clean profile and enable rewards.
- Note backup words.
- Note addresses displayed in Add Funds.
- Note paymentId, addresses, and CARD_ID from
ledger_state
. - Use restore functionality to Restore a wallet.
- Note backup words (they updated to the words from the restored wallet and are different than step 3).
- Note addresses in Add Funds (these are still the same as step 4).
- Open
ledger_state
and note paymentId (this was updated, so it’s different than step 5) addresses and CARD_ID (these are all still the same as step 5). At this point, you now have a paymentId/address discrepancy or mismatch. If you were to put the paymentId from step 9 into this URL: https://ledger.mercury.basicattentiontoken.org/v2/wallet/<paymentId> you can see what addresses should be displayed to compare to what is actually displayed. - Update to 0.59.28 Beta version.
- Navigate to Rewards page.
Actual result:
- Backup words for wallet match step 7 and paymentId matches step 9 (pass)
- Addresses in Add Funds are still the same as steps 4/8 (fail)
- Addresses and CARD_ID are still the same as steps 5/9 (fail)
Expected result:
Backup words/paymentId for wallet should be accurate Addresses in Add Funds should be updated to be the ones that correspond with the correct paymentID Addresses and CARD_ID should be updated to be the ones that correspond with the correct paymentID
Reproduces how often:
easily with steps above
Brave version (brave://version info)
Brave | 0.59.28 Chromium: 72.0.3626.64 (Official Build) beta(64-bit) |
---|---|
Revision | eaa9668e80ce5405e7f1902579558ea725c06ca1-refs/branch-heads/3626@{#708} |
OS | Mac OS X |
Reproducible on current release:
- Does it reproduce on brave-browser dev/beta builds? yes
Website problems only:
- Does the issue resolve itself when disabling Brave Shields?
- Is the issue reproducible on the latest version of Chrome?
Additional Information
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (8 by maintainers)
Top GitHub Comments
@LaurenWags will check it out and ping you tomorrow to see what is going on
Verified passed with
Verification passed on
Used test plan from https://github.com/brave/brave-core/pull/1508
Verification passed on