<p>The second argument in the <code>sendrawtransaction</code> RPC is <code>maxfeerate</code> specified expressed in the unit <code>[BTC/kvB]</code>.</p>
<pre><code>100,000 BTC/kvB = 100 BTC/vB = 10,000,000,000 sat/vB
</code></pre>
<p>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 <a href="https://bitcoincore.org/en/doc/27.0.0/rpc/rawtransactions/sendrawtransaction/" rel="nofollow noreferrer">documentation states</a>, if you are willing to accept <em>any</em> 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.</p>

CC BY-SA 4.0
2024-08-26T14:54:08.690Z
2024-08-26T14:54:08.690Z
Murch
<p>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?</p>

CC BY-SA 4.0
2024-08-23T12:39:03.853Z
What does your `debug.log` say after you submit the transaction? Is it perhaps a conflict?
Murch
CC BY-SA 4.0
2024-08-23T17:15:59.587Z
There is no error message, but the txid cannot be found in the debug.rog. However, the client. sendRawTransaction returned the txid. Is it possible that my transaction was not broadcasted? How can I make mempool or other mining pools receive my transaction
bit big
CC BY-SA 4.0
2024-08-23T18:07:03.767Z
Is your transaction non-standard? Anything special about it?
Murch
CC BY-SA 4.0
2024-08-23T19:17:00.210Z
This is a full RBF transaction with a rate exceeding 10000. Is there any platform that supports transactions with a rate exceeding 10000? Mempool.space will prompt "code": -25, "message": "Fee excesses maximum configured by user (e.g. - maxtxfee, maxfee)"
bit big
CC BY-SA 4.0
2024-08-23T22:39:15.493Z
Assuming you mean 10,000 sat/vB, you may be overpaying by a factor of 3,000× currently. That’s why the 1,000 sat/vB warning is implemented in some wallet software. Are you reprioritizing a parent transaction so that you actually want to pay that much?
Murch
<json-rpc><non-standard-transaction>
Local broadcast cannot be found in mempool
bit big
# Local broadcast cannot be found in mempool

(Asked by: username_0 on 2024-08-23)

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?

**Tags:** json-rpc, non-standard-transaction

> **Comments:**
> **username_1**: What does your `debug.log` say after you submit the transaction? Is it perhaps a conflict?  
> **username_0**: There is no error message, but the txid cannot be found in the debug.rog. However, the client. sendRawTransaction returned the txid. Is it possible that my transaction was not broadcasted? How can I make mempool or other mining pools receive my transaction  
> **username_1**: Is your transaction non-standard? Anything special about it?  
> **username_0**: This is a full RBF transaction with a rate exceeding 10000. Is there any platform that supports transactions with a rate exceeding 10000? Mempool.space will prompt "code": -25, "message": "Fee excesses maximum configured by user (e.g. - maxtxfee, maxfee)"  
> **username_1**: Assuming you mean 10,000 sat/vB, you may be overpaying by a factor of 3,000× currently. That’s why the 1,000 sat/vB warning is implemented in some wallet software. Are you reprioritizing a parent transaction so that you actually want to pay that much?  

---

## 1 answers

### Answer by username_1 on 2024-08-26. Score: 0

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](https://bitcoincore.org/en/doc/27.0.0/rpc/rawtransactions/sendrawtransaction/), 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.


---

