[RPC] sendrawtransaction should not check "mempool min fee not met" #16061

I tried to broadcast one transaction

Mempool:

{
  "size": 4168,
  "bytes": 2831662,
  "usage": 9274704,
  "maxmempool": 50000000,
  "mempoolminfee": 0.00003249,
  "minrelaytxfee": 0.00001000
}

Error:

mempool min fee not met, 1600 < 2547 (code 66)

Even if my mempool has enough space, a transaction sent through RPC has been rejected.

While I can understand why such rule apply to transactions coming from P2P, I don't understand why it should apply with transaction coming from sendrawtransaction. (Actually it should also not apply for whitelisted peer imho)

Such transaction should be, or at least able to pass bypass_limits to true.

If I get concept ACKs for this, I might do it.

In general, making RPC acceptance distinct from P2P acceptance means leaking information on transaction origin (as peers can observe a transaction coming from you which you wouldn't have accepted from someone else). Specifically, in this case we announce our min feerate through BIP133, making it obvious when we're violating it ourselves.

Shit that's good point.

Long term solution might be to keep it in the mempool but not broadcasting them until the fee filter goes down.