From: Erik Aronesty <erik@q32.com>
To: Antoine Riard <antoine.riard@gmail.com>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] [BIP Proposal] Reduced Data Temporary Softfork
Date: Wed, 29 Oct 2025 19:43:19 -0700 [thread overview]
Message-ID: <CAJowKgKBBa+vD=5X0VMV2OFiBBM23Ok6nmvfoLTr8fia141=FQ@mail.gmail.com> (raw)
In-Reply-To: <f07bc89c-fcf0-4e3c-85ab-593a509c1265n@googlegroups.com>
[-- Attachment #1: Type: text/plain, Size: 1449 bytes --]
>
>
> Case law in the USA regarding illegal content has always rested squarely
> on those who:
1 - provide broad public access, in this case a company like OpenSEA
(which has had to block content)
2 - the original author
if punishing "relays" was a thing, then every CISCO router, SMTP relay and
DISCORD server that provided access would be in court all day long
instead, it's the users of the illegal data and the publishers that
actually wind up in trouble - not the internet providers
the bitcoin ledger is neither a browser or web server, nor is it an image
uploader. there is zero ability to view images built into the system
and even if it was
the purpose of this software is to be a distributed and effectively
uncensorable ledger.
hopefully it doesn't change because someone launched a meme campaign with
vague threats of legal action
if a transaction has /no reasonable expectation of being mined/ (too
expensive to validate, too large, too low fees), there's also no reason to
relay it
this is probably the best way to set policy
--
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/CAJowKgKBBa%2BvD%3D5X0VMV2OFiBBM23Ok6nmvfoLTr8fia141%3DFQ%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 2082 bytes --]
next prev parent reply other threads:[~2025-10-30 2:57 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-25 20:43 dathonohm via Bitcoin Development Mailing List
2025-10-26 20:47 ` Jameson Lopp
2025-10-27 4:22 ` dathonohm via Bitcoin Development Mailing List
2025-10-27 12:14 ` Jameson Lopp
2025-10-27 16:35 ` TheWrlck
2025-10-26 22:27 ` Peter Todd
2025-10-27 3:41 ` Jal Toorey
2025-10-27 17:27 ` Max
2025-10-27 4:08 ` dathonohm via Bitcoin Development Mailing List
2025-10-27 18:29 ` Kyle Stout
2025-10-27 19:56 ` Greg Maxwell
2025-10-28 5:13 ` dathonohm via Bitcoin Development Mailing List
2025-10-30 0:31 ` Antoine Riard
2025-10-30 2:43 ` Erik Aronesty [this message]
2025-11-08 0:51 ` dathonohm via Bitcoin Development Mailing List
2025-11-08 3:43 ` Edil Guimarães de Medeiros
2025-11-08 9:30 ` 'Bitcoin Eagle' via Bitcoin Development Mailing List
2025-11-08 15:38 ` Greg Maxwell
2025-11-08 16:40 ` Daniel Buchner
2025-11-08 17:55 ` Chris Riley
2025-11-08 21:02 ` dathonohm via Bitcoin Development Mailing List
2025-11-08 21:39 ` Greg Maxwell
2025-11-09 20:07 ` dathonohm via Bitcoin Development Mailing List
2025-11-11 7:43 ` 'Bitcoin Eagle' via Bitcoin Development Mailing List
2025-11-11 16:23 ` Greg Maxwell
2025-11-09 1:21 ` Murch
2025-11-09 20:56 ` onyxcoyote
2025-11-09 21:34 ` Peter Todd
2025-11-10 19:46 ` Lucas Barbosa
2025-10-28 9:16 ` /dev /fd0
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='CAJowKgKBBa+vD=5X0VMV2OFiBBM23Ok6nmvfoLTr8fia141=FQ@mail.gmail.com' \
--to=erik@q32.com \
--cc=antoine.riard@gmail.com \
--cc=bitcoindev@googlegroups.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