From: Mike Hearn <mike@plan99•net>
To: "sickpig@gmail•com" <sickpig@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>,
Krzysztof Okupski <k.okupski@googlemail•com>
Subject: Re: [Bitcoin-development] Bitcoin Protocol Specification
Date: Mon, 14 Jul 2014 14:37:13 +0200 [thread overview]
Message-ID: <CANEZrP1FZjqpoOgJuNa4=_bar61=PCTeT8MqG9FGnpdKS=SCbw@mail.gmail.com> (raw)
In-Reply-To: <CA+c4Zoy-O_MkRZDVjHysDMhZnx8mo7XAAw7iJQYHrm9f4OsEUQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 504 bytes --]
>
> 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 everyone who tried it, didn't succeed :)
Heck even people who tried to reimplement it by reading the code keep
getting subtle details wrong.
So it should definitely be possible one day, assuming Bitcoin doesn't
become radically more complex, but it's a minefield.
[-- Attachment #2: Type: text/html, Size: 815 bytes --]
next prev parent reply other threads:[~2014-07-14 12:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 9:54 Krzysztof Okupski
2014-07-14 10:41 ` sickpig
2014-07-14 11:26 ` Mike Hearn
2014-07-14 11:41 ` Wladimir
2014-07-14 11:49 ` Mike Hearn
2014-07-14 12:25 ` sickpig
2014-07-14 12:37 ` Mike Hearn [this message]
2014-07-14 20:51 ` sickpig
-- strict thread matches above, loose matches on Subject: below --
2014-07-14 14:44 Krzysztof Okupski
2014-07-14 17:16 ` Jeff Garzik
2014-07-09 9:34 Krzysztof Okupski
2014-06-26 11:30 Krzysztof Okupski
2014-07-03 1:21 ` Isidor Zeuner
[not found] ` <CANVdSAqEyqavSHea3uhzVWGKQU0UHGZDVqEiF3Ox2XkhwM=zpA@mail.gmail.com>
2014-07-07 17:57 ` JMOlmos GMail
2014-07-08 15:29 ` Chris D'Costa
2014-07-08 20:04 ` Matt Whitlock
2014-07-08 21:08 ` Aaron Voisine
2014-07-08 22:40 ` Jorge Timón
2014-07-09 11:57 ` Mike Hearn
2014-05-18 13:35 Krzysztof Okupski
2014-05-18 14:38 ` Adam Back
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANEZrP1FZjqpoOgJuNa4=_bar61=PCTeT8MqG9FGnpdKS=SCbw@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=k.okupski@googlemail$(echo .)com \
--cc=sickpig@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox