> While it would be nice to have a library encapsulating the consensus code, > this > shouldn't come at the cost of safety, especially when the actual users of that > library or their needs is still uncertain.
While I agree that it shouldn't come at unreasonable risk, my whole reason for prioritizing the consensus library is that it is the first step toward the goal of isolating the consensus code completely. As soon as it exists in a repository by itself, it is easier to enforce a different regime of change control there, or even freeze it completely over time. To keep track of consensus changes one'd only have to follow that repository, instead of filter it between tons of GUI, RPC or utility commits. IMO having the consensus isolated into a portable self-contained library is the most important goal of Bitcoin Core project at this point. I've tried to keep the amount of unnecessary refactoring down, but some is unfortunately unavoidable. I'm sure we can find a way to rebase CHECKLOCKTIMEVERIFY so that it can land in 0.11. Wladimir ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development