From: Greg Maxwell <gmaxwell@gmail.com>
To: TwoLargePizzas <zarfius@gmail.com>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] The Cat, BIP draft discussion.
Date: Sat, 13 Dec 2025 15:02:30 +0000 [thread overview]
Message-ID: <CAAS2fgR91F1-3HuQ16iVoT9XeyrFXtZ94_t6bWUL0QbLNRVhHw@mail.gmail.com> (raw)
In-Reply-To: <2ebbf019-a562-427d-93af-b88f0cf5658an@googlegroups.com>
[-- Attachment #1: Type: text/plain, Size: 1237 bytes --]
On Sat, Dec 13, 2025 at 10:05 AM TwoLargePizzas <zarfius@gmail.com> wrote:
> If the rules don't matter, they won't be bothered if the rules change.
>
No, that kind of mutual exclusion is often not how things work and isn't
how they work here. They absolutely will be valued by this proposal
stealing their bitcoins, but their NFT grifting will not ultimately be
effected otherwise.
When you say "millions of dollars in funds" are you including the value of
> the NFTs tied to those sats
>
No, just the Bitcoin-- but you indirectly make a fine point that it
probably ought to be considered too. It's fine that you or I agree that
NFT crap isn't appropriate to bitcoin but those harmed aren't beholden to
your or my *opinion* and will absolutely seek redress through any and all
means for the damage caused to them.
--
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/CAAS2fgR91F1-3HuQ16iVoT9XeyrFXtZ94_t6bWUL0QbLNRVhHw%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 2065 bytes --]
next prev parent reply other threads:[~2025-12-13 15:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <32f8c689-314d-4a5e-9af6-2e3e704582e6n@googlegroups.com>
[not found] ` <CAAS2fgRR77nZj3-rJo70dnxe8Lma88-C9JqdVTYfXGHRgFu3pA@mail.gmail.com>
2025-12-11 20:54 ` Bitcoin Mechanic
2025-12-12 1:49 ` TwoLargePizzas
2025-12-13 15:02 ` Greg Maxwell [this message]
2025-12-14 1:51 ` Pepe Hodler
2025-12-15 10:35 ` Nona YoBidnes
2025-12-15 16:04 ` Greg Maxwell
2025-12-12 17:13 ` [bitcoindev] " Jonathan Voss
2025-12-12 23:40 ` Greg Maxwell
2025-12-13 3:54 ` Melvin Carvalho
2025-12-13 7:07 ` Ataraxia 009
2025-12-17 16:22 ` Jonathan Voss
2025-12-19 3:31 ` Greg Maxwell
2025-12-21 5:07 ` John
2025-12-23 19:12 ` Greg Maxwell
2025-12-24 17:19 ` waxwing/ AdamISZ
2025-12-30 14:36 ` Antoine Riard
2026-01-19 1:11 ` Pepe Hodler
2026-01-23 3:45 ` Chris Riley
2026-01-23 13:55 ` Galois Field
2026-01-22 1:14 ` Claire Ostrom
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=CAAS2fgR91F1-3HuQ16iVoT9XeyrFXtZ94_t6bWUL0QbLNRVhHw@mail.gmail.com \
--to=gmaxwell@gmail.com \
--cc=bitcoindev@googlegroups.com \
--cc=zarfius@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