From: Larry Ruane <larryruane@gmail•com>
To: vjudeu@gazeta•pl,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Surprisingly, Tail Emission Is Not Inflationary
Date: Mon, 11 Jul 2022 12:25:41 -0600 [thread overview]
Message-ID: <CAEpYn+egaW2YMjJfOSTcaquGNpLhYAqf4sBY83WUsynRwQE1cQ@mail.gmail.com> (raw)
In-Reply-To: <165002130-e93e1ef73ec867025cbf3ea9b2d142bc@pmq2v.m5r2.onet>
On Sun, Jul 10, 2022 at 3:05 AM vjudeu via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org> wrote:
>
> Not really, because people that run full nodes, just accepted Segwit
> and Taproot. They had no choice. And in case of zero satoshis, it could
> be the same: you would see zero if you look at raw bytes, but you will
> see non-zero values, if you use some upgraded client, that will support
> amount hiding, or other features.
>
> Segwit: old nodes see no new signatures, new nodes see all signatures
> Zero satoshis: old nodes see new zero amounts, new nodes see all amounts
>
> It is that simple.
I see what you mean, have the P2P messages depend on whether the peer
is running old code (doesn't know about tail emission) or new code
(does know about it).
I don't think this can work in this case. It worked for Segwit because
the P2P differences involved only signatures (which determine whether
the transaction is valid), not the *effect* of the transaction, that is,
how it changes the UTXO set. Consensus requires all nodes to always
agree on the UTXO set.
Larry Ruane
next prev parent reply other threads:[~2022-07-11 18:26 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 12:46 Peter Todd
2022-07-09 14:26 ` Eric Voskuil
2022-07-09 15:15 ` Peter Todd
2022-07-09 15:24 ` Eric Voskuil
2022-07-09 15:31 ` Peter Todd
2022-07-09 17:43 ` naman naman
2022-07-09 17:48 ` Peter Todd
2022-07-10 6:54 ` naman naman
2022-07-10 2:10 ` Tobin Harding
2022-07-10 7:08 ` vjudeu
2022-07-11 18:25 ` Larry Ruane [this message]
2022-07-10 10:18 ` Jacob Eliosoff
2022-07-11 2:32 ` Anthony Towns
2022-07-11 6:15 ` Stefan Richter
2022-07-11 10:42 ` Giuseppe B
2022-07-11 12:56 ` Erik Aronesty
2022-07-11 23:57 ` Anthony Towns
2022-07-13 18:29 ` Zac Greenwood
2022-07-11 16:59 ` Peter Todd
2022-07-11 17:44 ` Bram Cohen
2022-07-13 14:06 ` Alfred Hodler
2022-07-09 14:57 John Tromp
2022-07-09 15:13 ` Peter Todd
2022-07-11 18:44 ` Dave Scotese
2022-07-09 20:53 Eric Voskuil
2022-07-09 20:54 Eric Voskuil
2022-07-09 21:59 ` ZmnSCPxj
2022-07-10 14:17 ` alicexbt
2022-07-10 16:38 ` alicexbt
2022-07-10 17:29 ` Peter Todd
2022-07-10 17:27 ` Peter Todd
2022-07-10 18:12 ` vjudeu
2022-07-18 11:34 ` David A. Harding
2022-07-18 19:14 ` Erik Aronesty
2022-07-18 21:48 ` Eric Voskuil
2022-07-25 15:04 ` Erik Aronesty
2022-07-26 15:44 ` jk_14
2022-07-26 17:05 ` Erik Aronesty
2022-07-09 22:21 Peter
[not found] <mailman.80287.1657405305.8511.bitcoin-dev@lists.linuxfoundation.org>
2022-07-10 7:44 ` John Tromp
2022-07-10 17:42 Eric Voskuil
2022-07-19 18:36 Peter
2022-07-20 14:35 ` Eric Voskuil
2022-07-26 20:01 jk_14
2022-08-15 21:46 jk_14
2022-08-17 11:10 ` Erik Aronesty
2022-08-16 16:05 Peter
2022-08-19 17:21 ` aliashraf.btc At protonmail
2022-08-20 15:30 ` Billy Tetrud
2022-08-17 8:54 jk_14
2022-08-17 13:43 jk_14
2022-08-18 15:29 ` Breno Brito
2022-08-18 15:44 ` Billy Tetrud
2022-08-18 20:49 ` Erik Aronesty
2022-08-18 20:22 jk_14
2022-08-19 5:34 vjudeu
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=CAEpYn+egaW2YMjJfOSTcaquGNpLhYAqf4sBY83WUsynRwQE1cQ@mail.gmail.com \
--to=larryruane@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=vjudeu@gazeta$(echo .)pl \
/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