From: Sergio Demian Lerner <sergio.d.lerner@gmail•com>
To: Jules Lamur <jules.lamur@etu•umontpellier.fr>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Cc: denis.hodzhadzhikov@etu•umontpellier.fr, pompidor@lirmm•fr,
kim-son.pham01@etu•umontpellier.fr
Subject: Re: [bitcoin-dev] [BIP] Stratum protocol specification
Date: Mon, 12 Feb 2018 21:54:00 -0300 [thread overview]
Message-ID: <CAKzdR-q2sjUZ+E4RhMbscZWNKzFpmJW0LPyCrr8QKnpcz9jekw@mail.gmail.com> (raw)
In-Reply-To: <f07cd6df-da05-28d5-df41-5514e7a50db1@etu.umontpellier.fr>
[-- Attachment #1: Type: text/plain, Size: 1465 bytes --]
When we worked on the extensions for RSK merge mining, I prepared an
internal document with the most up to date Straum protocol description I
could get.
This is the document:
https://docs.google.com/document/d/1ocEC8OdFYrvglyXbag1yi8WoskaZoYuR5HGhwf0hWAY/edit?usp=sharing
Regards
On Fri, Feb 9, 2018 at 10:48 AM, Jules Lamur via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> Hello,
>
> With two student colleagues of mine (Denis HODZHADZHIKOV,
> Kim-Son PHAM), we are developping a mining pool as an
> academic work.
>
> Currently, most of our work is reverse engineering on existing
> implementations of the protocol because of the lack of
> documentation, especially on edge cases.
>
> Our referent professor suggested us to publish a IETF RFC draft
> of the protocol's specification. However, I think a BIP would be
> more appropriate for this.
>
> I've found that the BIP 40 and the BIP 41 were allocated for
> respectively the wire protocol and the mining protocol since
> at least August 2013 (cf.
> https://github.com/bitcoin/bips/commit/e12d37e6639a4acffa2710ddb6cf81
> e74403b2a1).
>
> It seems that nothing has been done since.
>
> Could we (me and my colleagues) start writing a draft for the
> BIP 41 (mining protocol)?
>
> Regards,
> Jules LAMUR.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 2394 bytes --]
prev parent reply other threads:[~2018-02-13 0:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 13:48 Jules Lamur
2018-02-13 0:54 ` Sergio Demian Lerner [this message]
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=CAKzdR-q2sjUZ+E4RhMbscZWNKzFpmJW0LPyCrr8QKnpcz9jekw@mail.gmail.com \
--to=sergio.d.lerner@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=denis.hodzhadzhikov@etu$(echo .)umontpellier.fr \
--cc=jules.lamur@etu$(echo .)umontpellier.fr \
--cc=kim-son.pham01@etu$(echo .)umontpellier.fr \
--cc=pompidor@lirmm$(echo .)fr \
/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