<p>minrelayfee is already in BTC/kB, so that's exactly what you need.</p>

<blockquote>
  <p>35kb tx with a tiny 0.0003 fee.</p>
</blockquote>

<p>Didn't do the math, but I think even the default minrelayfee should block those.</p>

CC BY-SA 3.0
2016-01-31T03:04:25.183Z
Ah okay, didn't know that, thanks. It's showing in my mempool, and my mempool is getting awfully large lately, over 30,000 txs. Thought maybe adding some like this could help...
m1xolyd1an
CC BY-SA 3.0
2016-02-01T02:50:42.100Z
Are you running a recent version? The relayfee stuff had been changed a bit over the past few versions. What is your current minrelayfee setting?
Jannes
CC BY-SA 3.0
2016-02-01T04:39:19.100Z
[relayfee] => 5.0E-5  (0.00005)
m1xolyd1an
CC BY-SA 3.0
2016-01-31T02:16:49.057Z
2016-01-31T02:16:49.057Z
Jannes
<p>Is it possible to configure a node to reject junk transactions like this
<a href="https://tradeblock.com/bitcoin/tx/6d67480fde2dd484b0ee389a6488db212ea7d0dbd2a11358efcc0b39077407ca" rel="nofollow">https://tradeblock.com/bitcoin/tx/6d67480fde2dd484b0ee389a6488db212ea7d0dbd2a11358efcc0b39077407ca</a></p>

<p>199 inputs, 35kb tx with a tiny 0.0003 fee. </p>

<p>There's <code>minrelaytxfee</code>, but I'm looking for something that is based on both fee and tx size. </p>

<transaction-fees><unconfirmed-transactions><mempool>
Reject TXs based on fee in comparison to TX size?
m1xolyd1an
# Reject TXs based on fee in comparison to TX size?

(Asked by: username_0 on 2016-01-30)

Is it possible to configure a node to reject junk transactions like this
<https://tradeblock.com/bitcoin/tx/6d67480fde2dd484b0ee389a6488db212ea7d0dbd2a11358efcc0b39077407ca>

199 inputs, 35kb tx with a tiny 0.0003 fee.

There's `minrelaytxfee`, but I'm looking for something that is based on both fee and tx size.

**Tags:** transaction-fees, unconfirmed-transactions, mempool


---

## 1 answers

### Answer by username_1 on 2016-01-31. Score: 1 | Accepted answer

minrelayfee is already in BTC/kB, so that's exactly what you need.

> 35kb tx with a tiny 0.0003 fee.

Didn't do the math, but I think even the default minrelayfee should block those.

> **Comments:**
> **username_0**: Ah okay, didn't know that, thanks. It's showing in my mempool, and my mempool is getting awfully large lately, over 30,000 txs. Thought maybe adding some like this could help...  
> **username_1**: Are you running a recent version? The relayfee stuff had been changed a bit over the past few versions. What is your current minrelayfee setting?  
> **username_0**: [relayfee] => 5.0E-5  (0.00005)  

---

