From: Luke Dashjr <luke@dashjr.org>
To: lautaro.dragan@gmail.com,
Lautaro Dragan <lautarodragan@gmail.com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Claiming an OP_RETURN Prefix
Date: Mon, 6 Aug 2018 02:04:18 +0000 [thread overview]
Message-ID: <201808060204.19511.luke@dashjr.org> (raw)
In-Reply-To: <CAK6DEspS1+LWwJgbVfWaM3gHwmhYPGBuV+dLPATe--QwmUUa2Q@mail.gmail.com>
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.com/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=OP_RETURN&oldid=62560> 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 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
next prev parent reply other threads:[~2018-08-06 2:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-05 21:11 [bitcoin-dev] Claiming an OP_RETURN Prefix Lautaro Dragan
2018-08-05 23:57 ` Peter Todd
2018-08-06 0:55 ` Lautaro Dragan
2018-08-06 1:54 ` CryptAxe
2018-08-06 2:04 ` Luke Dashjr [this message]
2018-08-06 2:19 ` Lautaro Dragan
2018-08-14 18:34 Christopher Allen
2018-08-15 20:33 ` Jorge Timón
2018-08-15 20:40 ` Jude Nelson
2018-08-15 21:54 ` Christopher Allen
2018-08-16 1:06 ` Luke Dashjr
2018-08-16 2:22 ` Lautaro Dragan
2018-08-16 2:37 ` Luke Dashjr
2018-08-16 17:32 ` Ryan Grant
2018-08-15 21:46 ` Peter Todd
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=201808060204.19511.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=lautaro.dragan@gmail.com \
--cc=lautarodragan@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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