📅 Original date posted:2021-04-17
📝 Original message:Peter, thanks for the links. I'm aware that there are other timestamping
aggregation services that already exist, but I had some different ideas
that integrate into some other services. Also thanks for sending the link
to the single use seal asset transfer. I will take a look at that.
On Sat, Apr 17, 2021 at 3:50 PM Peter Todd <pete at petertodd.org> wrote:
> On Sat, Apr 17, 2021 at 03:57:55AM +0000, Christopher Gilliard via
> bitcoin-dev wrote:
> > Thanks ZmnSCPxj. Yes, I agree there are many ways to embed arbitrary data
> > in the blockchain and it's not feasible to block all of them. That is why
> > it's important to, at the same time as limiting the OP_RETURN to one per
> > block, also propose and implement a layer 2 solution for timestamping
> > so people have a clear and simple upgrade path. That is what I will be
> > discussing in one of the BIPs I intend to release early next week.
>
> Note that an aggregated timestamping service already exists:
>
> https://petertodd.org/2016/opentimestamps-announcement
>
> But timestamping is useless for most things people want to do, as it can't
> commit to a unique history. It merely proves something existed in the
> past. For
> uniqueness, you need something like:
>
> https://petertodd.org/2017/scalable-single-use-seal-asset-transfer
>
>
> Anyway, at current fees being what they are there's no compelling reason
> to try
> to prevent people from embedding data in the Bitcoin block chain with
> consensus
> changes. Economics is preventing that just fine.
>
> --
> https://petertodd.org 'peter'[:-1]@petertodd.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20210417/618da7c6/attachment.html>;
Christopher Gilliard [ARCHIVE] /
npub1qm…0hwnt
2023-06-07 22:51:44
in reply to nevent1q…xvfm
Author Public Key
npub1qmsejphez6np2my9fu40kj9en68d5fa3s7ap4ul7eh9aeuljusgs50hwntPublished at
2023-06-07 22:51:44Event JSON
{
"id": "b0402b8b140047fb15fd24c67f5b4a1600f0e0303c247e5683f88141e77fde25",
"pubkey": "06e19906f916a6156c854f2afb48b99e8eda27b187ba1af3fecdcbdcf3f2e411",
"created_at": 1686178304,
"kind": 1,
"tags": [
[
"e",
"603f39678bcc9e8e30f94bfe6386763f2e249a0ec7bc1f247dad6d882215065d",
"",
"root"
],
[
"e",
"20464ed6bc77a10f3540d0bc7815194da79fd0cc5f9f09f59cbd57b71bae8f1e",
"",
"reply"
],
[
"p",
"daa2fc676a25e3b5b45644540bcbd1e1168b111427cd0e3cf19c56194fb231aa"
]
],
"content": "📅 Original date posted:2021-04-17\n📝 Original message:Peter, thanks for the links. I'm aware that there are other timestamping\naggregation services that already exist, but I had some different ideas\nthat integrate into some other services. Also thanks for sending the link\nto the single use seal asset transfer. I will take a look at that.\n\nOn Sat, Apr 17, 2021 at 3:50 PM Peter Todd \u003cpete at petertodd.org\u003e wrote:\n\n\u003e On Sat, Apr 17, 2021 at 03:57:55AM +0000, Christopher Gilliard via\n\u003e bitcoin-dev wrote:\n\u003e \u003e Thanks ZmnSCPxj. Yes, I agree there are many ways to embed arbitrary data\n\u003e \u003e in the blockchain and it's not feasible to block all of them. That is why\n\u003e \u003e it's important to, at the same time as limiting the OP_RETURN to one per\n\u003e \u003e block, also propose and implement a layer 2 solution for timestamping\n\u003e \u003e so people have a clear and simple upgrade path. That is what I will be\n\u003e \u003e discussing in one of the BIPs I intend to release early next week.\n\u003e\n\u003e Note that an aggregated timestamping service already exists:\n\u003e\n\u003e https://petertodd.org/2016/opentimestamps-announcement\n\u003e\n\u003e But timestamping is useless for most things people want to do, as it can't\n\u003e commit to a unique history. It merely proves something existed in the\n\u003e past. For\n\u003e uniqueness, you need something like:\n\u003e\n\u003e https://petertodd.org/2017/scalable-single-use-seal-asset-transfer\n\u003e\n\u003e\n\u003e Anyway, at current fees being what they are there's no compelling reason\n\u003e to try\n\u003e to prevent people from embedding data in the Bitcoin block chain with\n\u003e consensus\n\u003e changes. Economics is preventing that just fine.\n\u003e\n\u003e --\n\u003e https://petertodd.org 'peter'[:-1]@petertodd.org\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20210417/618da7c6/attachment.html\u003e",
"sig": "41b68dbe6161a2b6e0059ce52ea88b36b3cca9f75a5452527120d28c4810b21872d6d03c4a0ecec4d1d616ebf374fcadbb6e3ce27cc68c6699140b0eac9de616"
}