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] CLN Connection with Rune Shows Balances as NaN #2910

Closed
1 task done
kn0wmad opened this issue Dec 7, 2023 · 4 comments · Fixed by #2951 or #2995
Closed
1 task done

[BUG] CLN Connection with Rune Shows Balances as NaN #2910

kn0wmad opened this issue Dec 7, 2023 · 4 comments · Fixed by #2951 or #2995
Assignees

Comments

@kn0wmad
Copy link
Contributor

kn0wmad commented Dec 7, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

Balance and historical incoming tx amounts all show as NaN

Screenshots [optional]

image

Steps To Reproduce

  1. Connect via CLN with a Rune (in this case from StartOS)
  2. Connection completes successfully
  3. Balance and historical incoming tx amounts all show as NaN
    • Historical outbound tx amounts display properly

Expected behavior

Correct balances and payment history display in sats

Alby information

Alby 3.4.1 Firefox extension

Device information

Linux 6.1, Firefox 120

Additional context

No response

Are you working on this?

None

@kn0wmad
Copy link
Contributor Author

kn0wmad commented Jan 4, 2024

The balance issue has been fixed, however the NaN bug still remains for the tx history. Suggest re-open

image

@reneaaron reneaaron reopened this Jan 14, 2024
@pavanjoshi914
Copy link
Contributor

image

just had a quick test on cln. was unable to reproduce. what kind of transactions those are someone paying you rom specific website or something else?

@kn0wmad
Copy link
Contributor Author

kn0wmad commented Jan 17, 2024

Good thought - I rolled down and realized this is only happening on spam txs of 1sat, of which I've received a ton for some reason. These are all keysends. Legitimate txs (all > 1sat) are shown accurately. Hopefully this is helpful.

@pavanjoshi914
Copy link
Contributor

Good thought - I rolled down and realized this is only happening on spam txs of 1sat, of which I've received a ton for some reason. These are all keysends. Legitimate txs (all > 1sat) are shown accurately. Hopefully this is helpful.

thanks for helping us @kn0wmad! issue should be resolved in next release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants