public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "'Russell O'Connor' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Cc: Jonathan Voss <k98kurz@gmail.com>
Subject: Re: [bitcoindev] Proposal to solve the spam war: configurable data blob relay policy
Date: Tue, 27 May 2025 12:02:58 -0400	[thread overview]
Message-ID: <CAMZUoK=mux6u=f_b0yLb6nvJp41H7iPg7G+dLO5xT94kbDybjQ@mail.gmail.com> (raw)
In-Reply-To: <a2fde16d-5ddd-47ae-8b8f-6ca313d92b66n@googlegroups.com>

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

On Sat, May 24, 2025 at 5:33 PM Jonathan Voss <k98kurz@gmail.com> wrote:

> However, the recent discussion premised upon Citrea's Clementine Bridge
> evidences primarily that the relaying capabilities of the Bitcoin network
> itself are sufficiently useful for L2 designers that there is an incentive
> to bypass standardness restrictions for the sake of reliably promulgating
> data -- at least in the case of Citrea, they say they need to quickly and
> widely disseminate 140+ bytes of arbitrary ZKP data to recover from an
> invalid protocol state, and the utility of that ZKP data very quickly
> decreases after it has been confirmed and processed.


Does your proposal actually solve this problem?  Posting the 140 bytes of
data to the blockchain works as a public bulletin board because the actual
data within the block is what is ultimately guaranteed to be disseminated
to all participants.  With your proposal, a transaction with an OP_RETURN
containing a hash of data could end up being mined without the relevant
transaction ever even being relayed through the Bitcoin network.

-- 
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/CAMZUoK%3Dmux6u%3Df_b0yLb6nvJp41H7iPg7G%2BdLO5xT94kbDybjQ%40mail.gmail.com.

[-- Attachment #2: Type: text/html, Size: 2090 bytes --]

  parent reply	other threads:[~2025-05-27 16:05 UTC|newest]

Thread overview: 7+ 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 [this message]
2025-05-27 16:51   ` Jonathan Voss
2025-05-27 23:10     ` Dave Scotese
2025-05-28 13:16       ` Greg Sanders

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='CAMZUoK=mux6u=f_b0yLb6nvJp41H7iPg7G+dLO5xT94kbDybjQ@mail.gmail.com' \
    --to=bitcoindev@googlegroups.com \
    --cc=k98kurz@gmail.com \
    --cc=roconnor@blockstream.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