📅 Original date posted:2018-08-05
📝 Original message: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
Luke Dashjr [ARCHIVE] /
npub1tf…rfq0n
2023-06-07 18:13:59
in reply to nevent1q…s6nc
Author Public Key
npub1tfk373zg9dnmtvxnpnq7s2dkdgj37rwfj3yrwld7830qltmv8qps8rfq0nPublished at
2023-06-07 18:13:59Event JSON
{
"id": "3df8e73974fb5904a3941476851b51d4a578443a475f4b87d6564ca5da5854a2",
"pubkey": "5a6d1f44482b67b5b0d30cc1e829b66a251f0dc99448377dbe3c5e0faf6c3803",
"created_at": 1686161639,
"kind": 1,
"tags": [
[
"e",
"eccbd39bd966baef56b5939c955d566f9fe6d2296c2c463ce1c7b09a9df0388b",
"",
"root"
],
[
"e",
"c1ca2b08cb8a40b84b25596d644530be5f584034db3c1e65f9ef02105a0633d8",
"",
"reply"
],
[
"p",
"507d21660d41ec66a0e3e486a78a7369f474a388c0acebd70433bba44cd2a40d"
]
],
"content": "📅 Original date posted:2018-08-05\n📝 Original message:Are you doing coloured coins or storing data?\n\nIf the former, you should probably collaborate with the authors of BIP 160 \n(yet to be added to the main repo), and/or write a new BIP if BIP 160 is \ninsufficient for some reason.\n\nIf the latter, you just shouldn't do it at all.\n\nNote that BIPs need to specify an actual protocol, not just claim a prefix.\n\n\nOn Sunday 05 August 2018 21:11:26 Lautaro Dragan via bitcoin-dev wrote:\n\u003e Hi everyone,\n\u003e\n\u003e My name's Lautaro and I'm currently acting as Tech Lead of Po.et\n\u003e \u003chttps://en.bitcoin.it/wiki/OP_RETURN#OP_RETURN_prefixes\u003e. At Po.et we use\n\u003e colored coins\n\u003e \u003chttps://github.com/poetapp/node/blob/3c905bc5dbd3722ad39ac68041d9f2a099e5e\n\u003e84c/src/BlockchainWriter/ClaimController.ts#L101-L110\u003e to\n\u003e store data on the Bitcoin blockchain with prefix \"POET\".\n\u003e\n\u003e I've read in an old version of the OP_RETURN entry of the bitcoin wiki\n\u003e \u003chttps://en.bitcoin.it/w/index.php?title=OP_RETURN\u0026oldid=62560\u003e that\n\u003e *protocols wishing to claim OP_RETURN prefixes should use the standard\n\u003e Bitcoin Improvement Proposals process*.\n\u003e\n\u003e That entry seems to have changed recently\n\u003e \u003chttps://en.bitcoin.it/wiki/OP_RETURN#OP_RETURN_prefixes\u003e, no longer\n\u003e stating that we should follow the BIP process, and I haven't been able to\n\u003e find any existing BIP claiming an OP_RETURN prexif, but for the sake of\n\u003e thoroughness I'd like to ask for your help or confirmation here.\n\u003e\n\u003e Should we actually be using the BIP process to claim a prefix?\n\u003e\n\u003e Thanks in advance,\n\u003e\n\u003e Lautaro",
"sig": "f5161dee310310f986624012a174fc1e9e76394cdf61d43a36d971d5004561e2303a7ce18067ff5874ec7e092831f52e280a78e603e9d161da04a0a041691321"
}