<p>A bitcoin network fork occur when a block generated by one node is not accepted by a percentage of nodes, those nodes will split and continue working on its own.</p>

<p>This change will not cause a fork, it will cause that some transactions will be discarded by some nodes, older nodes will never include it on a block but newer nodes will and older nodes will accept a block with transactions different transaction fees as those are not checked for block validity.</p>

<p>This has already happened, pools can discard transactions without fees or ask for higher fees than usual for example and the block will be valid and included in the blockchain without problems. </p>

CC BY-SA 3.0
2014-01-19T13:39:40.580Z
Thanks, so nothing as extreme as a hard fork, but a Tx with the "wrong" fee will not be accepted by older nodes? Makes the network a bit rocky doesn't it?
pinhead
CC BY-SA 3.0
2014-01-19T14:05:26.507Z
Well that's the problem/virtue of P2P networks, everyone can run it's own node and while you follow the protocol nobody should bother you about your specific implementation. Just now there are several differnent teams working on alternative implementations of the reference client, they will differ for sure on some things but is great to be able to choose the best client for your needs.
frisco
CC BY-SA 3.0
2014-01-19T13:36:12.623Z
2014-01-19T13:36:12.623Z
frisco
<p>So if the core devs change the minimum fee schedule, lowering the maximum "free" tx from 10,000 to 1,000 bytes - how will that not cause a hard fork? Or at least prevent nodes running old software from propagating a new Tx?</p>

<p><a href="https://github.com/bitcoin/bitcoin/blob/master/src/main.cpp" rel="nofollow">https://github.com/bitcoin/bitcoin/blob/master/src/main.cpp</a></p>

<p>I could be reading this wrong, but looks to me like the minimum fee schedule is part of the "standard tx" test, and so nodes with different fee schedules wouldn't be able to send all tx's between each other.</p>

<transaction-fees>
Is the minimum fee considered when a full P2P node validates a Tx?
pinhead
# Is the minimum fee considered when a full P2P node validates a Tx?

(Asked by: username_0 on 2014-01-19)

So if the core devs change the minimum fee schedule, lowering the maximum "free" tx from 10,000 to 1,000 bytes - how will that not cause a hard fork? Or at least prevent nodes running old software from propagating a new Tx?

<https://github.com/bitcoin/bitcoin/blob/master/src/main.cpp>

I could be reading this wrong, but looks to me like the minimum fee schedule is part of the "standard tx" test, and so nodes with different fee schedules wouldn't be able to send all tx's between each other.

**Tags:** transaction-fees


---

## 1 answers

### Answer by username_1 on 2014-01-19. Score: 1 | Accepted answer

A bitcoin network fork occur when a block generated by one node is not accepted by a percentage of nodes, those nodes will split and continue working on its own.

This change will not cause a fork, it will cause that some transactions will be discarded by some nodes, older nodes will never include it on a block but newer nodes will and older nodes will accept a block with transactions different transaction fees as those are not checked for block validity.

This has already happened, pools can discard transactions without fees or ask for higher fees than usual for example and the block will be valid and included in the blockchain without problems.

> **Comments:**
> **username_0**: Thanks, so nothing as extreme as a hard fork, but a Tx with the "wrong" fee will not be accepted by older nodes? Makes the network a bit rocky doesn't it?  
> **username_1**: Well that's the problem/virtue of P2P networks, everyone can run it's own node and while you follow the protocol nobody should bother you about your specific implementation. Just now there are several differnent teams working on alternative implementations of the reference client, they will differ for sure on some things but is great to be able to choose the best client for your needs.  

---

