From: "'moonsettler' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
To: defenwycke <cal.defenwycke@gmail.com>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Re: segOP potential BIP discussion
Date: Sat, 01 Nov 2025 12:00:26 +0000 [thread overview]
Message-ID: <3S1IMGSH6z-3Ho81Ugp9o-ltTwpIC-4ow6bn6aEAtK4XrkG5HTkvTw0BeZFpPILfabdp7rz_LDHEBWX_XZk0a7nKR4sJRUp_3B7pAMaJ86I=@protonmail.com> (raw)
In-Reply-To: <a5ec8a97-3884-40eb-9276-8536f664c0e0n@googlegroups.com>
Hi Defenwycke,
I think this is not a horrible idea, there might be future demand for a pruneable proof of publication space.
But, your proposal does not provide an incentive for anyone to adopt it. If it was cheaper than witness space,
I think it would be a serious consideration especially for rollups.
The idea that the bytes incur full cost (4WU) makes it on arrival economically speaking.
Also it's a bit unclear how consensus and nodes in sync would interact with the "recent window".
It's a reasonable approach to mandate the presence of such an extension block near the chain-tip, but
nodes by default should not download or verify it during IBD. This would only add a constant burden to nodes,
while allowing bitcoin to scale on higher layers more that require such proof of publication mechanism for
their security.
Thinking that this would be used by graffiti type payloads that especially are seeking the permanence, persistence
and replication of bitcoin transactional data, or that metaprotocols that want to use the block space as an archival
layer for their own token ledgers is I'm afraid completely misguided or even delusional.
BR,
moonsettler
--
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/3S1IMGSH6z-3Ho81Ugp9o-ltTwpIC-4ow6bn6aEAtK4XrkG5HTkvTw0BeZFpPILfabdp7rz_LDHEBWX_XZk0a7nKR4sJRUp_3B7pAMaJ86I%3D%40protonmail.com.
prev parent reply other threads:[~2025-11-01 12:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 23:40 [bitcoindev] " defenwycke
2025-10-30 21:25 ` [bitcoindev] " defenwycke
2025-11-01 12:00 ` 'moonsettler' via Bitcoin Development Mailing List [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='3S1IMGSH6z-3Ho81Ugp9o-ltTwpIC-4ow6bn6aEAtK4XrkG5HTkvTw0BeZFpPILfabdp7rz_LDHEBWX_XZk0a7nKR4sJRUp_3B7pAMaJ86I=@protonmail.com' \
--to=bitcoindev@googlegroups.com \
--cc=cal.defenwycke@gmail.com \
--cc=moonsettler@protonmail.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