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

wallet: change getwalletinfo RPC 'balance' to be confirmed balance, i… #508

Conversation

ca98am79
Copy link
Contributor

…nstead of repeating unconfirmed balance

see issue #505

@@ -752,7 +752,7 @@ class RPC extends RPCBase {
return {
walletid: wallet.id,
walletversion: 6,
balance: Amount.coin(balance.unconfirmed, true),
balance: Amount.coin(balance.confirmed, true),
Copy link
Member

Choose a reason for hiding this comment

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

Ok my thinking on this: Let's not break backwards compatibility by changing what is returned here. We don't want to mess up any application relying on this value always being the "safest" (confirmed) balance.

What I think could be useful is just adding more values. We already have unconfirmed_balance, let's just add confirmed_balance and spendable_balance (combine with #507)

@nodech nodech closed this Dec 9, 2021
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.

3 participants