From: Greg Tonoski <gregtonoski@gmail.com>
To: vjudeu@gazeta.pl
Cc: "bitcoin-dev@lists.linuxfoundation.org"
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] [BUG]: Bitcoin blockspace price discrimination put simple transactions at disadvantage
Date: Tue, 16 Jan 2024 11:40:48 +0100 [thread overview]
Message-ID: <CAMHHROzbQQ1MeegD5_jO8gkyXKLKH+wvgjPKVANYEG=0NT58jQ@mail.gmail.com> (raw)
In-Reply-To: <173813261-12d93c171dc593da018492a4fc8f3f2b@pmq8v.m5r2.onet>
On Wed, Dec 27, 2023 at 10:43 PM <vjudeu@gazeta.pl> wrote:
>
> I think it should be fixed. Because now, sending coins into P2WPKH is cheaper than sending them to P2TR, even though finally, when those coins are spent, the blockspace usage is cheaper for Taproot (when you spend by key) than for Segwit, because public key hash is not stored anywhere. But of course, because the cost is splitted between sender and spender, it is more profitable to send to P2WPKH, and spend from P2TR.
The difference between P2WPKH and P2TR is a different topic, I think.
A single bloated transaction would be treated with higher priority
than a number of simple transactions of the same total size and fee -
irrespectively of P2WPKH and P2TR type.
next prev parent reply other threads:[~2024-01-16 10:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 21:43 [bitcoin-dev] [BUG]: Bitcoin blockspace price discrimination put simple transactions at disadvantage vjudeu
2024-01-16 10:40 ` Greg Tonoski [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-27 16:44 Greg Tonoski
2023-12-27 19:06 ` Nagaev Boris
2024-01-13 15:04 ` Greg Tonoski
2024-01-16 23:29 ` Nagaev Boris
2024-01-21 17:14 ` Greg Tonoski
2023-12-27 22:39 ` Keagan McClelland
2024-01-14 13:10 ` Greg Tonoski
2024-01-16 23:40 ` Nagaev Boris
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='CAMHHROzbQQ1MeegD5_jO8gkyXKLKH+wvgjPKVANYEG=0NT58jQ@mail.gmail.com' \
--to=gregtonoski@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=vjudeu@gazeta.pl \
/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