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

[BUG] Browser notifications miscalculate #3192

Closed
1 task done
itstomekk opened this issue Jul 14, 2024 · 0 comments · Fixed by #3194
Closed
1 task done

[BUG] Browser notifications miscalculate #3192

itstomekk opened this issue Jul 14, 2024 · 0 comments · Fixed by #3194
Assignees

Comments

@itstomekk
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

I'm sending from Alby to other wallets, amount X sats.
It shows on a transaction history that I paid X, but it actually charged me X plus FEES.
Ok.

However, in Google Chrome notifications (they appear in system notifications) it displays that I paid amount X minus FEES, and that I also paid those fees (which sums to X, not to X + fees), which is incorrect.

Compare below last two transactions
left: Alby (extension and web app both display same amounts)
right: Chrome (Windows) notifications
image


Btw, when I'm sending from another node (here: Blink),
then on transaction history it shows I've spent X+FEES (which is what was actually charged), and the Chrome notification shows "Successfully paid X".

Screenshots [optional]

No response

Steps To Reproduce

  1. Enable notifications for Alby extension in your browser
  2. Send 1000 sats to anoter node/wallet
  3. Compare transaction records in Alby web or extension, with records in these notifications.

Expected behavior

We don't tell users about fees in our interfaces, simply charge them from their balance.
We tell them only (?) in these notifications - but it's incorrect.

Alby information

3.8.1

Device information

Windows, Chrome

Additional context

No response

Are you working on this?

None

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 a pull request may close this issue.

2 participants