0

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.

Improve this question
1

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.

Improve this answer
2
  • 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
    Jan 19 '14 at 13:39
  • 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
    Jan 19 '14 at 14:05

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.