Closed bitspill closed 4 years ago
I am in favor of making this change, it should make it much easier for people to make sure that their floData is included in the TX signature by default. As I have recently been doing some research I have observed that currently almost all transactions are excluding the floData from the signature. I assume that most FLO users use FLOcore to create the transactions, either through QT or the JSON-RPC.
Do we have a release timeline that we are thinking about for this PR?
All 0.10.4 nodes should be off the network by now following the hard fork back in April - this PR changes the default to now sign floData for all transactions rather than only segwit
Unsigned floData sent by old nodes or other libraries that may not be signing yet are still accepted - this only enables extra protections by default instead of being explicitly opt-in