I'll pick up where you left off, Jeff. The thought process behind the
Bitcoin Core threading model, platform support, libification, dependency
management, core data structures, DoS mitigation, script evolution,
scalability roadmap... just to scratch the surface, is likely never going
to be apparent
[[Since I sent this while the List Server was down, it didn't actually go
to everyone. Forgive me if you ended up with two copies.]]
Peter provides an excellent summary of Proof of Publication, which starts
with defining it as being composed of a solution to the double spend
problem. He requires
On Mon, Dec 15, 2014 at 3:52 PM, Peter Todd wrote:
>> Comparisons with the SPV security of sidechains are fallacious. The
>> alternative to a proof-of-publication system reliant on client-side
>> validation is a blockchain. The question of whether the token used on
>> said blockchain should be two
> I don't care which tabbing style or column width you pick, but **pick one**,
> and enforce it across the entire codebase.
See https://github.com/bitcoin/bitcoin/pull/5387
Wladimir
--
Download BIRT iHub F-Type - The Fre
On Wed, Dec 10, 2014 at 3:45 PM, Austin Walne wrote:
> I've had these same questions myself. I'm happy to write up some
> documentation this afternoon. I can draft something based on this thread.
> What other key terminology should be included?
Fanquake already started on that (but didn't even
5 matches
Mail list logo
