Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 72059D2A for ; Mon, 6 Aug 2018 02:19:58 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-wm0-f67.google.com (mail-wm0-f67.google.com [74.125.82.67]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id E281E1A0 for ; Mon, 6 Aug 2018 02:19:57 +0000 (UTC) Received: by mail-wm0-f67.google.com with SMTP id c14-v6so12189184wmb.4 for ; Sun, 05 Aug 2018 19:19:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=s1nbtctfnZ6y+5RS9zuGlcPcxOod/zxtUIFrEVdQDiI=; b=d4+O+xUirM6lb73sDitg0hbFuydMg0CYcP6HJtdsGEOqM5I1ruNxaSvhdKd6Ny8tG1 XrMsjpvp/bGdkP7H1zTepXu9Jd0e3AYOokB/qMSeVitswXQAuaJOZkixwn7tCojf2T4u LWdD1L3N/uWxIEjHYMCWX6tcssBNNDbY/9N1zrhTPJ1DwAWssFt77OU9JhW8AGX49OYY qrC+7xyCwbWTJD5KvoHuN84OvwiW8Qk4jL4qzaxoRapX/wxavKEVvjpn4RvVbESEkaUy vFGkxSFbP8BS/t3YMMz21Sic2ilCcg+IWBDGzEHM6XQywY2+x6zp+RGS9bArNiysEbR4 iXMQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc; bh=s1nbtctfnZ6y+5RS9zuGlcPcxOod/zxtUIFrEVdQDiI=; b=KzD10ikOLhXq4F1n248yCAa/VP7mIuXacxP/39qObW+asXVWp/J1q9OtQGTosP9Qhr fkZNO3tc0kHyMpL+GHpNI6ydBB3AAwTyheC0fX8k7Hnn8/o7/MXa87JJNfdnXCoAObpA HyVRo59KHJN4EpZCVFWqtab3LVcvY9MbRDtS+h94RNXFto8Vk9vzBpYD93l90VdYq9XB drrgwdIeo6cu+0+4Zon+UDgqOkebQX5+Y8bCvD0LvtVfXn7NORhjHqTywhtVK8ajD6uL q3VBwH3VhFlDWOoefly8WZIbCCOmqzq7twBui6ph6FiVN470/+Fhyf3/w/+C1WjuAE/0 gKmw== X-Gm-Message-State: AOUpUlG6u3SU1bGe+Cc+g/pIC1xG8MVlXTTRCJwjvETDj9RzmuJ2/v7i zfDsk/5atGfG2fVn6a2SLF/JyE4inZIF7JV77r/vdQ== X-Google-Smtp-Source: AAOMgpdLZQxYPaSzLyCYdh1pYf+XJzvBw4fLZ2JnkbYGABwHoKdgocuXP5TV76JKwCEUi48WD+b1ePvBlkQ+G7B2jSo= X-Received: by 2002:a1c:1805:: with SMTP id 5-v6mr3757394wmy.25.1533521996352; Sun, 05 Aug 2018 19:19:56 -0700 (PDT) MIME-Version: 1.0 References: <201808060204.19511.luke@dashjr.org> In-Reply-To: <201808060204.19511.luke@dashjr.org> Reply-To: lautaro.dragan@gmail.com From: Lautaro Dragan Date: Sun, 5 Aug 2018 23:19:44 -0300 Message-ID: To: Luke Dashjr Content-Type: multipart/alternative; boundary="000000000000d9101f0572bae9a7" X-Spam-Status: No, score=-1.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,FREEMAIL_REPLYTO,HTML_MESSAGE, RCVD_IN_DNSWL_NONE autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Mon, 06 Aug 2018 03:02:54 +0000 Cc: Bitcoin Protocol Discussion Subject: Re: [bitcoin-dev] Claiming an OP_RETURN Prefix 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: Mon, 06 Aug 2018 02:19:58 -0000 --000000000000d9101f0572bae9a7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sorry for the confusion. We're doing coloured coins =E2=80=94 storing the "= POET" prefix followed by an IPFS hash in the output and storing the full data in IPFS. Would you point me to the current work on BIP 160 or the authors? El dom., 5 de ago. de 2018 a la(s) 23:05, Luke Dashjr escribi=C3=B3: > Are you doing coloured coins or storing data? > > If the former, you should probably collaborate with the authors of BIP 16= 0 > (yet to be added to the main repo), and/or write a new BIP if BIP 160 is > insufficient for some reason. > > If the latter, you just shouldn't do it at all. > > Note that BIPs need to specify an actual protocol, not just claim a prefi= x. > > > On Sunday 05 August 2018 21:11:26 Lautaro Dragan via bitcoin-dev wrote: > > Hi everyone, > > > > My name's Lautaro and I'm currently acting as Tech Lead of Po.et > > . At Po.et we > use > > colored coins > > < > https://github.com/poetapp/node/blob/3c905bc5dbd3722ad39ac68041d9f2a099e5= e > >84c/src/BlockchainWriter/ClaimController.ts#L101-L110> to > > store data on the Bitcoin blockchain with prefix "POET". > > > > I've read in an old version of the OP_RETURN entry of the bitcoin wiki > > tha= t > > *protocols wishing to claim OP_RETURN prefixes should use the standard > > Bitcoin Improvement Proposals process*. > > > > That entry seems to have changed recently > > , no longer > > stating that we should follow the BIP process, and I haven't been able = to > > find any existing BIP claiming an OP_RETURN prexif, but for the sake of > > thoroughness I'd like to ask for your help or confirmation here. > > > > Should we actually be using the BIP process to claim a prefix? > > > > Thanks in advance, > > > > Lautaro > > --000000000000d9101f0572bae9a7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Sorry for the confusion. We're doing coloured coi= ns =E2=80=94 storing the "POET" prefix followed by an IPFS hash i= n the output and storing the full data in IPFS.

Would you point me to the current work on BIP 160 or the authors?
El dom., 5 de ago. de 2018 a = la(s) 23:05, Luke Dashjr <luke@dashjr.org> escribi=C3=B3:
Are you doing coloured coins or storing data?

If the former, you should probably collaborate with the authors of BIP 160 =
(yet to be added to the main repo), and/or write a new BIP if BIP 160 is insufficient for some reason.

If the latter, you just shouldn't do it at all.

Note that BIPs need to specify an actual protocol, not just claim a prefix.=


On Sunday 05 August 2018 21:11:26 Lautaro Dragan via bitcoin-dev wrote:
> Hi everyone,
>
> My name's Lautaro and I'm currently acting as Tech Lead of Po.= et
> <https://en.bitcoin.it/wiki/OP_RETURN= #OP_RETURN_prefixes>. At Po.et we use
> colored coins
> <https://github.co= m/poetapp/node/blob/3c905bc5dbd3722ad39ac68041d9f2a099e5e
>84c/src/BlockchainWriter/ClaimController.ts#L101-L110> to
> store data on the Bitcoin blockchain with prefix "POET".
>
> I've read in an old version of the OP_RETURN entry of the bitcoin = wiki
> <https://en.bitcoin.it/= w/index.php?title=3DOP_RETURN&oldid=3D62560> that
> *protocols wishing to claim OP_RETURN prefixes should use the standard=
> Bitcoin Improvement Proposals process*.
>
> That entry seems to have changed recently
> <https://en.bitcoin.it/wiki/OP_RETURN= #OP_RETURN_prefixes>, no longer
> stating that we should follow the BIP process, and I haven't been = able to
> find any existing BIP claiming an OP_RETURN prexif, but for the sake o= f
> thoroughness I'd like to ask for your help or confirmation here. >
> Should we actually be using the BIP process to claim a prefix?
>
> Thanks in advance,
>
> Lautaro

--000000000000d9101f0572bae9a7--