egun writing code to implement
what was described in the liked post, but I'm sure he will reply to
you since he's subscribed to this mailing list.
>
>
>
> From: sick...@gmail.com
> Sent: Monday, June 15, 2015 12:18 PM
> To: Raystonn .
> Cc: Bitcoin Dev
> Subject
Sorry for top posting and the brevity but I'm typing from my phone
You shoud be interested in this post by Justus Ranvier then:
https://bitcoinism.liberty.me/economic-fallacies-and-the-block-size-limit-part-2-price-discovery/
On Jun 15, 2015 8:57 PM, "Raystonn ." wrote:
> I have been toying wit
On Mon, Jul 14, 2014 at 2:37 PM, Mike Hearn wrote:
> just out of curiosity, do you think it will be possible to create any
>> other proper protocol specifications rather than the C++ original?
>
>
> Well it's a finite code base so yes, it should be possible.
>
> The only problem is so far
On Mon, Jul 14, 2014 at 1:26 PM, Mike Hearn wrote:
> Nice work, but please don't call it the "Bitcoin protocol spec". Your
> document is not a spec.
fair objection, fwiw.
> It is an attempt to describe in English the Bitcoin
> protocol, but anyone who implemented it based on your description wou
On Mon, Jul 14, 2014 at 11:54 AM, Krzysztof Okupski
wrote:
> Dear all,
>
> thank you for your invaluable feedback. As requested, the spec
> will from now on be under version control. It can be found under:
>
> https://github.com/minium/Bitcoin-Spec
>
> The old link to the PDF will be, just in case
Hi,
On Mon, Feb 10, 2014 at 12:28 PM, Drak wrote:
> What is the official response from the Bitcoin Core developers about MtGox's
> assertion that their problems are due to a fault of bitcoin, as opposed to a
> fault of their own?
>
> The technical analysis preluding this mess, was that MtGox was
6 matches
Mail list logo
