Thinking out loud here : would it make sense to separate the consensus code into some kind of "Bitcoin Kernel" (similar to the Linux Kernel) project that could be used by anyone ?<div><br></div><div>Bitcoin Core (and any other application wishing to do so) could be based on it. </div><div><br></div><div>The kernel would just contain the absolute minimum code for reaching consensus, leaving every other aspects of the implementation to the applications built with it.</div><div><br></div><div>It would be stateless : it would provide an interface to submit a block/transaction to be validated, including the context needed to validate it (the previously validated blocks referenced by this block/transaction).</div><div><br></div><div>What do you think ?</div><div><br></div><div>Clément</div><div><br><div class="gmail_quote">Le Fri Nov 07 2014 at 9:49:05 AM, Peter Todd <<a href="mailto:pete@petertodd.org" target="_blank">pete@petertodd.org</a>> a écrit :</div><div class="gmail_quote"><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Fri, Nov 07, 2014 at 09:07:47AM +0100, Tamas Blummer wrote:<br>
> Peter,<br>
><br>
> forking would work best with a freeze of the consensus code. Do you see any chance for that?<br>
<br>
To a first approximation the consensus code *is* frozen; if we introduce<br>
any consensus changes into it at this point it's due to a mistake, not<br>
intentionally.<br>
<br>
Of course, that's not including the two serious soft-fork proposals in<br>
the air right now, Pieter Wuille's BIP62 and my CHECKLOCKTIMEVERIFY.<br>
However dealing with proposed changes like those in an environment where<br>
the competing implementations all use essentially the same<br>
consensus-critical code is much easier than in an environment where they<br>
don't; I say this on both a technical and political level.<br>
<br>
--<br>
'peter'[:-1]@<a href="http://petertodd.org" target="_blank">petertodd.org</a><br>
00000000000000000c901eb1b6b765<u></u><u></u>519b99c3afd7a9062ff4cfa29666ce<u></u><u></u>140d<br>
------------------------------<u></u><u></u>------------------------------<u></u><u></u>------------------<br>
______________________________<u></u><u></u>_________________<br>
Bitcoin-development mailing list<br>
<a href="mailto:Bitcoin-development@lists.sourceforge.net" target="_blank">Bitcoin-development@lists.<u></u>sour<u></u>ceforge.net</a><br>
<a href="https://lists.sourceforge.net/lists/listinfo/bitcoin-development" target="_blank">https://lists.sourceforge.net/<u></u><u></u>lists/listinfo/bitcoin-<u></u>develop<u></u>ment</a><br>
</blockquote></div></div>