Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 53DE110BF for ; Tue, 13 Feb 2018 00:54:44 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-lf0-f50.google.com (mail-lf0-f50.google.com [209.85.215.50]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 586C118A for ; Tue, 13 Feb 2018 00:54:43 +0000 (UTC) Received: by mail-lf0-f50.google.com with SMTP id f136so22868921lff.8 for ; Mon, 12 Feb 2018 16:54:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=BXr2bta9tH20NnT5/XPENb+2BOFYq++NIqJBhQRzHO8=; b=Wy/C/jzYUZU3tABvrkOxmxB//Un1IeCovJkZoV88CI9mk6R7cCSf/SPs6qU/guasV3 J2wbXD4lwg8dnP6uqOFe/yE2dfv45CAmUMQzwkTmHM3ddW/msoP84ANKDZtU0UbTLTXT /5/wzb0SLuIP1aFATK1cORMcNCCNcKzIjCnPsGGICnh3K1fOlE0g0Ah0nJvNVn457jD+ 2pAavdbjrwSCA5FOUvZCjFTUECouJBYKlLtlUQn0Jm+pNvT1+7q4gxCiUOu6dSWtquCO QIwoEcaKTmaXnQ6ipJKUquoovcl0NyP+qKJqIaUeR1a2axHt12KGlSzlsyDHJ/BhIIgr s+TQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=BXr2bta9tH20NnT5/XPENb+2BOFYq++NIqJBhQRzHO8=; b=lGPk0LUw4t8p8hv5cKI5ybZSEWTz0VDKAjtobjes3qnYXKCkfiobsMZXsZFAbKEPx0 Fb9b+TH1/pbNCbtQDOBfAZ5FOnBrOop6cy49N77fueg0zd9m0gIRQZdsmMQ7eCEW3xS/ 0Nc3yx9PTqPDPllrWxOyRRvFuh0fa60b6xUlpek7VfsJhVNZlVLK/5e4iU/G1/cSkApC X1xh0TAHRLxUI1HMVmdaglUild2lS0gUn94956yIQ7EHHk59BSlkZb1FyTM/KZzF5/9F JVTlPjAGoWq5t3tKydUjZxY6ibrFtgwK/2wY+TNgJUrhHCO07MwQe1UCn7rO1eRDRIY/ cQMw== X-Gm-Message-State: APf1xPB+rfJ3piByFlUBCPFVQ68q6J4UE771aJ5/4dEMYshigiMJlwO2 rxoh25qIIktD/YNkPp5Iq/4r7bjK7IXb83LBH00= X-Google-Smtp-Source: AH8x2271zqg5OpLkf5dc56CozlK0l3UHYYEepXH4yXLi8h/UqYfHqxwMmDF1tgzWBQC+XtuyShpbrKBHJlo5QdoypQg= X-Received: by 10.46.69.4 with SMTP id s4mr8414373lja.73.1518483281494; Mon, 12 Feb 2018 16:54:41 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.147.145 with HTTP; Mon, 12 Feb 2018 16:54:00 -0800 (PST) In-Reply-To: References: From: Sergio Demian Lerner Date: Mon, 12 Feb 2018 21:54:00 -0300 Message-ID: To: Jules Lamur , Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="001a114b109897491e05650d7014" X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Tue, 13 Feb 2018 00:57:04 +0000 Cc: denis.hodzhadzhikov@etu.umontpellier.fr, pompidor@lirmm.fr, kim-son.pham01@etu.umontpellier.fr Subject: Re: [bitcoin-dev] [BIP] Stratum protocol specification X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Feb 2018 00:54:44 -0000 --001a114b109897491e05650d7014 Content-Type: text/plain; charset="UTF-8" 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 > --001a114b109897491e05650d7014 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
When we worked on the extensions for RSK merge mining, I p= repared an internal document with the most up to date Straum protocol descr= iption I could get.
=
On Fri, Feb 9, 2018 at 10:48 AM, Jules Lamur= via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.or= g> 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/bi= tcoin/bips/commit/e12d37e6639a4acffa2710ddb6cf81e74403b2a1).

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

--001a114b109897491e05650d7014--