Local broadcast cannot be found in mempool
Local broadcast cannot be found in mempool
Loading saved threads...
bit big · External communityPost link
External question — Bitcoin Stack Exchange
Author: bit big
Original post: https://bitcoin.stackexchange.com/questions/124032
License: CC BY-SA 4.0 — https://creativecommons.org/licenses/by-sa/4.0/
Adaptation: HTML converted to plain text; contact email addresses removed.
After sending a raw transaction (SendRawTransaction (raw_tx, 100000)) and after local broadcasting, the transaction does not show up on platforms such as mempool.space. What might be the reason?
Quote
Report
Murch · External communityPost link
External answer — Bitcoin Stack Exchange
Author: Murch
Original post: https://bitcoin.stackexchange.com/a/124071
License: CC BY-SA 4.0 — https://creativecommons.org/licenses/by-sa/4.0/
Adaptation: HTML converted to plain text; contact email addresses removed.
The second argument in the
sendrawtransaction
RPC is
maxfeerate
specified expressed in the unit
[BTC/kvB]
.
100,000 BTC/kvB = 100 BTC/vB = 10,000,000,000 sat/vB
The value of 100,000 BTC/kvB that you provided is vastly in excess of sane feerates, so it looks like your node may have not broadcast the transaction to prevent overspending. As the
documentation states
, if you are willing to accept
any
feerate, you can set the second parameter to 0. I would however encourage you to carefully validate that your transaction is sending the remaining amount from the inputs to change outputs, which is a commonly overlooked issue with using raw transactions, as the combination of accepting any feerate and forgetting to specify a change output may lead to the majority of your funds being dropped to the transaction fees.
Quote
Report
Post Reply
Quoted from Forex.com.bd-Editorial External answer — Bitcoin Stack Exchange Author: Murch Source score (net votes, not local likes): 0 Original post: https://bitcoin.stackexchange.com/a/124071 License: CC BY-SA 4.0 — https://creativecommons.org/licenses/by-sa/4.0/ Adaptation: HTML converted to plain text; contact email addresses removed. The second argument in the sendrawtransaction RPC is maxfeerate specified expressed in the unit [BTC/kvB] . 100,000 BTC/kvB = 100 BTC/vB = 10,000,000,000 sat/vB The value of 100,000 BTC/kvB that you provided is vastly in excess of sane feerates, so it looks like your node may have not broadcast the transaction to prevent overspending. As the documentation states , if you are willing to accept any feerate, you can set the second parameter to 0. I would however encourage you to carefully validate that your transaction is sending the remaining amount from the inputs to change outputs, which is a commonly overlooked issue with using raw transactions, as the combination of accepting any feerate and forgetting to specify a change output may lead to the majority of your funds being dropped to the transaction fees.
Checking account access…