Watch-only, balance not "available" for psbt #83

issue SimpleAristocrats opened this issue on September 5, 2020
  1. SimpleAristocrats commented at 1:12 PM on September 5, 2020: none

    <!-- This issue tracker is only for technical issues related to Bitcoin Core. General bitcoin questions and/or support requests are best directed to the Bitcoin StackExchange at https://bitcoin.stackexchange.com. For reporting security issues, please read instructions at https://bitcoincore.org/en/contact/. If the node is "stuck" during sync or giving "block checksum mismatch" errors, please ensure your hardware is stable by running memtest and observe CPU temperature with a load-test tool such as linpack before creating an issue! -->

    <!-- Describe the issue -->

    Expected behavior

    Be able to create a psbt with a watch-only balance.

    <!--- What behavior did you expect? -->

    Actual behavior

    Entering any amount yields an error message : "The amount exceeds your balance".

    <!--- What was the actual behavior (provide screenshots if the issue is GUI-related)? -->

    To reproduce

    • Created a new watch-only wallet with bitcoin-qt (with "disable private keys")
    • Imported an address (segwit p2sh) in the console
    • Rescanned the blockchain (in the console)
    • Bitcoin-qt sees my "balance" in the "overview" screen and in the "send" screen (bottom-right corner of the send screen)
    • In the send screen : if I click "Use available balance", the amount stays at zero.
    • No coins shown in "Inputs" (coin control feature).
    • I tried to send an amount that's less than my balance (in the address being watched in watch-only mode) but I only get the error message "The amount exceeds your balance". For example, trying to send 2000 sats with a low transaction fee (of 2123 sat/kB) on a watch-only balance of more than 50 000 sats.
    • I do see the "create unsigned" button in the bottom-left corner. amount-exceeds-your-balance

    <!--- How reliably can you reproduce the issue, what are the steps to do so? -->

    System information

    Xubuntu 18.04.5 Bitcoin Core 0.20.1

    <!-- What version of Bitcoin Core are you using, where did you get it (website, self-compiled, etc)? -->

    <!-- What type of machine are you observing the error on (OS/CPU and disk type)? -->

    <!-- GUI-related issue? What is your operating system and its version? If Linux, what is your desktop environment and graphical shell? -->

    <!-- Any extra information that might be useful in the debugging process. -->

    <!--- This is normally the contents of a `debug.log` or `config.log` file. Raw text or a link to a pastebin type site are preferred. -->

  2. SimpleAristocrats added the label Bug on Sep 5, 2020
  3. Sjors commented at 1:39 PM on September 7, 2020: member

    The error message may be misleading. Exactly how did you import the address? I suggest using importmulti, include the witnessscript and be sure to set keypool to true.

  4. SimpleAristocrats commented at 11:24 PM on September 7, 2020: none

    Thank you very much.

    Exactly how did you import the address?

    I used importaddress in the console: importaddress "3...." "label" false and then rescanned the blockchain from the relevant blockheight (rescanblockchain 600000). I thought maybe that was the cause (not a full rescan) so I later tried that as well.

    My goal was to :

    1. use an airgapped coldcard hardware wallet (without usb, with only a microSD) to produce addresses completely offline,
    2. be able to watch them with bitcoin core, and
    3. later be able to use bitcoin core (online) to do a psbt transaction for signature on the airgapped coldcard,
    4. all without exporting-importing the xpub.

    Unfortunately, I don't see any way to get the witness script directly from the coldcard. I see by your answer that I misunderstood what is necessary to construct the psbt. Thank you very much for your time answering my issue!

  5. hebasto commented at 5:48 PM on March 6, 2021: member

    ping @achow101

  6. furszy commented at 1:48 PM on May 15, 2023: member

    Same as in https://github.com/bitcoin/bitcoin/issues/27659. I'm quite sure that this was solved by https://github.com/bitcoin/bitcoin/pull/26699 (which solved https://github.com/bitcoin/bitcoin/issues/26687).

    Ping me otherwise and will give it a look.

  7. hebasto closed this on May 18, 2023

  8. bitcoin-core locked this on May 17, 2024

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin-core/gui. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-29 09:20 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me