From: Tom Harding <tomh@thinlink•com>
To: Erik Aronesty <erik@q32•com>
Cc: bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] [Mempool spam] Should we as developers reject non-standard Taproot transactions from full nodes?
Date: Tue, 9 May 2023 14:06:00 -0700 [thread overview]
Message-ID: <2360b8ad-ac13-f180-fc95-4d5804184dd8@thinlink.com> (raw)
In-Reply-To: <CAJowKgLJ5WSVBKPzWEiZFUcB1jZG2PWBNMyMXRdHXaZdAsHeoQ@mail.gmail.com>
On 5/9/23 09:32, Erik Aronesty via bitcoin-dev wrote:
> obviously it's easy enough to evade if every non-economic user simply > keeps enough bitcoin around and sends it back to himself > > so
maybeit's a useless idea? but maybe that's enough of a hassle to stop >
people (it certainly breaks ordinals, since it can never be 1 sat)
Padding the change is not just a hassle, it requires holding extra BTC
in a hot wallet, which has a cost.
Spenders could also get around the rule by paying miners off-network,
but having to do so would be an appropriate penalty for broadcasting a
non-economic transaction.
next prev parent reply other threads:[~2023-05-09 21:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-07 17:22 Ali Sherief
2023-05-08 12:33 ` Michael Folkson
2023-05-08 12:58 ` Erik Aronesty
2023-05-08 17:13 ` Michael Folkson
2023-05-08 19:31 ` Ali Sherief
2023-05-08 19:47 ` Erik Aronesty
2023-05-08 20:36 ` Michael Folkson
2023-05-08 20:59 ` Erik Aronesty
2023-05-08 21:01 ` Erik Aronesty
2023-05-09 15:21 ` Tom Harding
2023-05-08 16:37 ` Melvin Carvalho
2023-11-03 10:15 ` Brad Morrison
2023-11-03 10:39 ` Melvin Carvalho
2023-11-04 9:58 ` ArmchairCryptologist
2023-05-08 22:37 ` Luke Dashjr
2023-05-09 0:02 ` Peter Todd
2023-05-09 1:43 ` Ali Sherief
2023-05-09 16:32 ` Erik Aronesty
2023-05-09 21:06 ` Tom Harding [this message]
2023-05-10 20:44 ` Keagan McClelland
2023-05-09 8:41 jk_14
2023-05-09 12:50 ` Erik Aronesty
2023-05-10 3:08 ` Weiji Guo
2023-05-11 13:12 Aleksandr Kwaskoff
2023-05-12 9:36 jk_14
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=2360b8ad-ac13-f180-fc95-4d5804184dd8@thinlink.com \
--to=tomh@thinlink$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=erik@q32$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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