From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp3.osuosl.org (smtp3.osuosl.org [IPv6:2605:bc80:3010::136]) by lists.linuxfoundation.org (Postfix) with ESMTP id 5D41DC002D for ; Mon, 11 Jul 2022 18:26:20 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp3.osuosl.org (Postfix) with ESMTP id 2952960F27 for ; Mon, 11 Jul 2022 18:26:20 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 2952960F27 Authentication-Results: smtp3.osuosl.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20210112 header.b=qgfhiV3J X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.099 X-Spam-Level: X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from smtp3.osuosl.org ([127.0.0.1]) by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 59veP0T1B-3f for ; Mon, 11 Jul 2022 18:26:19 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 66BBC60ECB Received: from mail-oa1-x34.google.com (mail-oa1-x34.google.com [IPv6:2001:4860:4864:20::34]) by smtp3.osuosl.org (Postfix) with ESMTPS id 66BBC60ECB for ; Mon, 11 Jul 2022 18:26:19 +0000 (UTC) Received: by mail-oa1-x34.google.com with SMTP id 586e51a60fabf-fe023ab520so7664738fac.10 for ; Mon, 11 Jul 2022 11:26:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=vOCOx0lmwxtHP2md3W9Mo+FYa1uCLefDvN3TDyjNQI4=; b=qgfhiV3JgTAZYyuz7WS1OJM3hP2bcTWYF7kyyCieYEJuNzubIeM3wKVaefxJpm6QAz f0eQrrLCYZAHKlRl3iqQcWne3R37e2P9Dm9ita/9cXuuyvXr2y4omNRjqD866GEWfTiW us1TS67rzTjy/G2WBrNRQNfZDmVGGyADC6jde7EQYcbsBmriV8A7KZ8r+R9bTnWmC6TO TOwWaoG4VvjS+P1noVuodM849gp/4ZIZdaRAJ1jsvnyIaiLxYwRdqyR/as+jRTfxC7Aq Z3g0OYeW+Qs6DIjur2WakJWVvw/0vZgteuz6xumlyw6jd3ZXcVQk701AP6J5LqFBptBU sJQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=vOCOx0lmwxtHP2md3W9Mo+FYa1uCLefDvN3TDyjNQI4=; b=eAFEXxZPk47r0yybuspCAMI77+TrtYACTSMA3HoFQSWAq6eXWtKfmNdGAdbcK+yZQh B462hlRD/N57bLnEWeeb7/InXaIYhp85li9tWTfsahum9cwmMGEjvyLNDBp1Q2j+YwxU iJTB3nck897dgH2p7Gasj8NnsAh1USGQaNLNlC52xzo496mDo/tXPvfDO2hozGSXLdI7 rOOuk1KvXD1IAP5kgjsyXEqOQ+JLLYefSzCSumkqVHTEloGD8R+pQvY4aDT9MiGkx1XZ Rj6tAR8HJuOQ/qjXSAF8meGdVO6zmB452Opxs7KIq9cDw+UcYjwDbo+BE8ZGgp+zThqQ +xzQ== X-Gm-Message-State: AJIora8LJuq/0gaQIMLieaoCgq/SuOFlQMpLFeAPISQorSKso5bl0ZSP 2UZDZz8pmlsRvfEQRjHqLZhQix5BWzK9nB9RC+w= X-Google-Smtp-Source: AGRyM1v+8jOD3hxxAj2yxBpYuO4PA4FMqaA0ZWZwJ/bEALK5uXq3pbnx18ZVaOQuyJqL0esIMylngFRA1pD9x490g3A= X-Received: by 2002:a05:6870:d0c2:b0:10b:fcf8:1273 with SMTP id k2-20020a056870d0c200b0010bfcf81273mr8247633oaa.211.1657563978362; Mon, 11 Jul 2022 11:26:18 -0700 (PDT) MIME-Version: 1.0 References: <165002130-e93e1ef73ec867025cbf3ea9b2d142bc@pmq2v.m5r2.onet> In-Reply-To: <165002130-e93e1ef73ec867025cbf3ea9b2d142bc@pmq2v.m5r2.onet> From: Larry Ruane Date: Mon, 11 Jul 2022 12:25:41 -0600 Message-ID: To: vjudeu@gazeta.pl, Bitcoin Protocol Discussion Content-Type: text/plain; charset="UTF-8" X-Mailman-Approved-At: Mon, 11 Jul 2022 23:06:01 +0000 Subject: Re: [bitcoin-dev] Surprisingly, Tail Emission Is Not Inflationary X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jul 2022 18:26:20 -0000 On Sun, Jul 10, 2022 at 3:05 AM vjudeu via bitcoin-dev 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