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 10:44 AM, Krzysztof Okupski
wrote:
> I've renamed it to "Bitcoin Developer Specification" a little while ago.
> Maybe it should rather be named "Bitcoin Developer Reference"? Either
> way, creating a good description of Bitcoin is an incremental process
> and there are cert
I've renamed it to "Bitcoin Developer Specification" a little while ago.
Maybe it should rather be named "Bitcoin Developer Reference"? Either
way, creating a good description of Bitcoin is an incremental process
and there are certainly many quirks I'm not aware of. I hope that
together we will soo
>
> 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 wh
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
Ah, that's great. Still, it would be good to be careful with the word
"specification".
On Mon, Jul 14, 2014 at 1:41 PM, Wladimir wrote:
> > As a loose description of the protocol for newbies it's an invaluable
> > resource and perhaps we should link to it from the developer guide.
>
> It has al
> As a loose description of the protocol for newbies it's an invaluable
> resource and perhaps we should link to it from the developer guide.
It has already been linked from the developer guide for quite a while,
under Additional Resources.
Wladimir
--
Nice work, but please don't call it the "Bitcoin protocol spec". Your
document is not a spec. It is an attempt to describe in English the Bitcoin
protocol, but anyone who implemented it based on your description would get
it wrong. For example you didn't mention the SIGHASH_SINGLE bug and many
othe
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
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, kept updated as well.
Warm greetings,
Krzysztof Okupski
-
On Tue, Jul 8, 2014 at 10:04 PM, Matt Whitlock
wrote:
> Is anyone working on a similar specification document for Satoshi's P2P
> protocol? I know how blocks and transactions are structured and verified,
> but I'm interested in knowing how they're communicated over the network.
There's a high
Dear all,
thank you for your words of encouragement. I'll upload
the raw .tex files on github shortly. If you have any other
proposals, please let me know. Especially if there are any
suggestions on how the signature section can be revised.
More information on network functionality can be found o
There's this (not sure how complete it is):
https://en.bitcoin.it/wiki/Protocol_specification
Also there's a good introduction to technical details here:
https://bitcointalk.org/index.php?topic=375524.0
I hope that is useful.
On 7/8/14, Matt Whitlock wrote:
> Is anyone working on a similar sp
I wrote down a really short description in code comments for
breadwallet, based on what I figured out:
https://github.com/voisine/breadwallet/blob/master/BreadWallet/BRPeer.m#L318
Aaron Voisine
breadwallet.com
On Tue, Jul 8, 2014 at 1:04 PM, Matt Whitlock wrote:
> Is anyone working on a simil
Is anyone working on a similar specification document for Satoshi's P2P
protocol? I know how blocks and transactions are structured and verified, but
I'm interested in knowing how they're communicated over the network.
This is probably the best, most complete resource available for those who
don't want to (or don't know how to) wade through the code. Well done.
On 7 July 2014 19:57, JMOlmos GMail wrote:
> And for translation's facility :P
>
>
> 2014-07-07 14:57 GMT-03:00 JMOlmos GMail :
>
>> And for translati
And for translation's facility :P
2014-07-07 14:57 GMT-03:00 JMOlmos GMail :
> And for translation's facility :P
>
>
> 2014-07-02 22:21 GMT-03:00 Isidor Zeuner :
>
> Hello Krzysztof,
>>
>> [...]
>> > As before, it can be found under:
>> >
>> > http://enetium.com/resources/Bitcoin.pdf
>> >
>> > I
Hello Krzysztof,
[...]
> As before, it can be found under:
>
> http://enetium.com/resources/Bitcoin.pdf
>
> I hope it will prove useful to the community and thank in advance
> for any further improvement proposals.
>
I think it's great work and provides a good reference for those
who want to get
Dear all,
a while ago I've posted a work of mine, namely the Bitcoin Protocol
Specification,
that should by now ring a bell to some of you. Ever since I've received
plenty of
comments from Bitcoin Core developers, Bitcoin enthusiasts and many others.
For the encouraging words and improvement propo
Suggestion: maybe you want to write and post here a paragraph summarizing
the topic of your paper so people can know if they feel qualified and if
they need to review it from their interests.
Adam
On Sun, May 18, 2014 at 03:35:33PM +0200, Krzysztof Okupski wrote:
>Dear all,
>
>I'd like to kindly
Dear all,
I'd like to kindly ask, those of you that have a bit of spare time, to
take a look at a Bitcoin protocol specification I've written. It is still
in development and, as some of you have already indicated, needs
improvement. I'd be very thankful if some of you could take the
time to review
21 matches
Mail list logo
