public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Peter Todd <pete@petertodd.org>
To: Greg Sanders <gsanders87@gmail.com>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Proposal to solve the spam war: configurable data blob relay policy
Date: Mon, 2 Jun 2025 10:25:43 +0000	[thread overview]
Message-ID: <aD18J2cP4x-ddzwD@petertodd.org> (raw)
In-Reply-To: <2a40a751-d0d1-4dc8-9dd5-67b7652ed8b8n@googlegroups.com>

[-- Attachment #1: Type: text/plain, Size: 2553 bytes --]

On Wed, May 28, 2025 at 06:16:20AM -0700, Greg Sanders wrote:
> > If we need two networks, one for stuff like what Citrea is doing and the 
> other for finance with a technological fence around it, I'm all for it. Has 
> Citrea heard of nostr?
> 
> Citrea, like Lightning, is relying on Bitcoin's proof of publication to 
> ultimately move bitcoin. Moving the data elsewhere would change the L2's 
> security model drastically.

FYI I wrote a fair bit about proof-of-publication started in 2013, over a
decade ago:

https://petertodd.org/2013/disentangling-crypto-coin-mining
https://petertodd.org/2014/setting-the-record-proof-of-publication

Putting data in the Bitcoin chain creates a proof that an overwhelming amount
of hash power has "seen" the data; in practice it's proof that everyone who
could ever want a copy of that data has a copy of it.

Lesser schemes simply can't provide that kind of guarantee. So it should be no
surprise that high-value use-cases like Citrea - or even NFTs - choose to use
Bitcoin as a publication layer.

That said, it would be interesting to see some schemes with lesser security
guarantees get developed. Bitmessage for example tried to develop a message
publication layer for anonymous messaging. But, notably, the last release of
Bitmessage is over 7 years ago, and I've been told that the software basically
doesn't work any more and old messages have all been lost.

Data published to the Bitcoin chain a decade ago can still easily be recovered.
A case in point: https://bitcoinstrings.com/


If someone does want to make a serious attempt at developing a new type of
proof-of-publication system, I'd strongly suggest focusing on the proof aspect:
make sure that your underlying cryptography actually proves that a given bit of
data is widely published. For example, if the system is based on sacrificing
Bitcoin to make data valuable, prove that other, previously published, data was
also published by using some kind of proof-of-posession like a random sampling
of a merkle tree of previously published data to show that all data in the
system had reached the wide audience that it is supposed to.

-- 
https://petertodd.org 'peter'[:-1]@petertodd.org

-- 
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/aD18J2cP4x-ddzwD%40petertodd.org.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2025-06-02 10:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-24 21:07 [bitcoindev] Proposal to solve the spam war: configurable data blob relay policy Jonathan Voss
2025-05-27 14:16 ` Pieter Wuille
2025-05-27 16:40   ` Jonathan Voss
2025-05-27 16:02 ` 'Russell O'Connor' via Bitcoin Development Mailing List
2025-05-27 16:51   ` Jonathan Voss
2025-05-27 23:10     ` Dave Scotese
2025-05-28 13:16       ` Greg Sanders
2025-06-02 10:25         ` Peter Todd [this message]

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=aD18J2cP4x-ddzwD@petertodd.org \
    --to=pete@petertodd.org \
    --cc=bitcoindev@googlegroups.com \
    --cc=gsanders87@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