-
Notifications
You must be signed in to change notification settings - Fork 145
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
Fix available balance for BRC-20 while sending #4703
Comments
I took a look at this and I don't have Of my supposed 100M SATS I only have 99211647 available for transfer so I think that could be happening here |
Because BRC-20 operates outside the norms of bitcoin, there's no concept of dust, as far as I know (so long as the inscription transfer itself is inscribed on a UTXO above network dust threshold). |
OK thanks Kyran! Reading into it a bit more(via our own tooltip) and I figured out the balance we show on the asset list is: I tracked back this work to this PR but it's light on details
When I check in my wallet in the asset list it says I have 100M SATS but then I only have 99,211,647 available for transfer so I think that could be happening here. You can see below I have some inscriptions which are included in my asset list balance but excluded from my total balance |
I have a wallet that has 1000 Fara When I see the balance of FARA it is 1000 When I click send the available balance is 950 fara (the other 50 is already made transferable). This is the complete situation: We should consider showing BRC-20 (for example $FARA) Balance and Transferable amount separately in the balance overview. Especially new users have trouble making sense of this. Some users do not realize they have already created a send inscription and the next step is to send that inscription and then they are surprised the balance is 950 instead of 1000. |
Let's tackle this as part of the send UX redesign project more broadly. |
I'm closing this issue since we intend to disable BRC-20 sends per #5773 |
E.g. here I'm seeing 4 BIMB under balances and in the token picker when initiating sending, but then it shows up as 0 BIMB in the form:
Screen.Recording.2023-12-15.at.07.07.04.mov
The text was updated successfully, but these errors were encountered: