1

I sent transaction with bitcoin-cli:

bitcoin-cli sendtoaddress tb1q3qlv7k648hec866a0x395hq0h3sqcg2lrq5r0k 0.001

As an answer I've got transaction Id.

But it still has no confirmation (a few hours).

Bellow are some details:

Network: signet.

Bitcoin core 25.0.0

Blockchain is synced.

Transaction:

 {
     "address": "tb1q3qlv7k648hec866a0x395hq0h3sqcg2lrq5r0k",
     "category": "send",
     "amount": -0.00100000,
     "vout": 0,
     "fee": -0.00014100,
     "confirmations": 0,
     "trusted": false,
     "txid": "f0aaf3aeca4590521557ce20bf12f2f8b4ec2520bebc45ab7958f87f08965c2f",
     "wtxid": "4c053b7ac21b0c86febb427d377d57b5397c4e4884c8a2397d1c3405b6ab7040",
     "walletconflicts": [
     ],
     "time": 1701862331,
     "timereceived": 1701862331,
     "bip125-replaceable": "yes",
     "abandoned": false   
}

bitcoin.conf:

    chain=signet
    blocksonly=1
    daemon=1
    dbcache=4000
    txindex=1
    debug=1
    logips=1
    fallbackfee=0.001

What can be wrong?

5
  • What RPC did you use, and what error did you receive back?
    – Murch
    Dec 6, 2023 at 19:33
  • I've got no errors. How can I check my RPC? Dec 6, 2023 at 20:11
  • 1
    @MikkiUkraine Please update your question to include what you are trying to achieve, how you are doing that, what do you expect to see, and what you are seeing instead? It is entirely unclear from your current question what the problem is. Dec 6, 2023 at 20:15
  • @PieterWuille Updated Dec 6, 2023 at 20:47
  • I took the liberty to edit the title of your question to be closer to what was happening. Feel free to suggest edit/revert if that doesn't capture your intent. Dec 7, 2023 at 18:18

1 Answer 1

1

You're running in blocksonly mode, which by default disables the broadcasting of wallet transactions. This is for privacy reasons: in blocksonly mode you don't participate in general in transaction relay. If then suddenly your node is seen broadcasting a transaction anyway, it would be very apparent to your peers that the transaction is yours.

Possible solutions:

  • Disable blocksonly mode.
  • Forcibly enable wallet broadcasting (walletbroadcast=1 in the config file), accepting the privacy risk.
  • Manually broadcast the transaction through sendrawtransaction.

There does exist a wallet rebroadcast mechanism, which will occasionally (every 12 to 36 hours) broadcast unconfirmed wallet transactions again (if wallet broadcasting is enabled at all). So if you disable blocksonly mode, or enable wallet broadcasting, and restart, the transaction should eventually make it out. The third option is a lot faster though.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.