<p>The following transactions are not broadcastable with the default bitcoin core configuration but could be found in new mined blocks:</p>
<ul>
<li>Transactions whose fee is smaller than 1 sat/vB (and RBF bumps that increment less than 1 sat/B).</li>
<li>Transactions with size greater than 100 vkB (and smaller than ~ 1 vMB)</li>
<li>Transactions with outputs amounts smaller than 566 satoshis (dust limit)</li>
<li>Transactions that are considered non-standard (I will try to list them because this is a very broad category)</li>
<li>Transactions with scriptSigs larger than 1650 B (and smaller than 10kB)</li>
<li>Transactions with more than one OP_RETURN output or an OP_RETURN output bigger than 83 B.</li>
<li>Transactions with scriptPuKeys of bare n-of-m multisigs, where m &gt; 3.</li>
<li>Transactions with scriptPubKeys or ScriptSigs that make the transaction malleable.</li>
</ul>

CC BY-SA 4.0
2020-07-13T08:15:33.790Z
2020-07-13T08:49:31.080Z
2020-07-13T08:49:31.080Z
Pedro
<p>Many valid transactions are not broadcastable by default in bitcoin core to avoid attacks that could harm the network. These would rarely be found in a node's mempool but could, however, be found in blocks because they don't violate any consensus rules.</p>
<p>What transactions fit these criteria?</p>

CC BY-SA 4.0
2020-07-13T02:01:21.133Z
Another one that comes to mind is a transaction with too many unconfirmed ancestors
Raghav Sood
CC BY-SA 4.0
2020-07-13T03:40:32.353Z
Hi Pedro, our platform tends to work poorly for questions that preconceive the answer. You may get more interesting answers if you reduce this post to the question portion and post your suggested answer as an answer post. Self-answers are encouraged! This would give other users a better chance to write a comprehensive answer rather than responding to the answer you already preformulated in your question.
Murch
CC BY-SA 4.0
2020-07-13T08:16:39.573Z
Thanks for the suggestion @Murch , I moved it that part to an answer.
Pedro
<bitcoin-core><transactions><mempool><validation><non-standard-transaction>
What valid transactions are not broadcastable?
Pedro
# What valid transactions are not broadcastable?

(Asked by: username_0 on 2020-07-13)

Many valid transactions are not broadcastable by default in bitcoin core to avoid attacks that could harm the network. These would rarely be found in a node's mempool but could, however, be found in blocks because they don't violate any consensus rules.

What transactions fit these criteria?

**Tags:** bitcoin-core, transactions, mempool, validation, non-standard-transaction

> **Comments:**
> **username_1**: Another one that comes to mind is a transaction with too many unconfirmed ancestors  
> **username_2**: Hi username_0, our platform tends to work poorly for questions that preconceive the answer. You may get more interesting answers if you reduce this post to the question portion and post your suggested answer as an answer post. Self-answers are encouraged! This would give other users a better chance to write a comprehensive answer rather than responding to the answer you already preformulated in your question.  
> **username_0**: Thanks for the suggestion @username_2 , I moved it that part to an answer.  

---

## 1 answers

### Answer by username_0 on 2020-07-13. Score: 2

The following transactions are not broadcastable with the default bitcoin core configuration but could be found in new mined blocks:

* Transactions whose fee is smaller than 1 sat/vB (and RBF bumps that increment less than 1 sat/B).
* Transactions with size greater than 100 vkB (and smaller than ~ 1 vMB)
* Transactions with outputs amounts smaller than 566 satoshis (dust limit)
* Transactions that are considered non-standard (I will try to list them because this is a very broad category)
* Transactions with scriptSigs larger than 1650 B (and smaller than 10kB)
* Transactions with more than one OP\_RETURN output or an OP\_RETURN output bigger than 83 B.
* Transactions with scriptPuKeys of bare n-of-m multisigs, where m > 3.
* Transactions with scriptPubKeys or ScriptSigs that make the transaction malleable.


---

