Larry Ruane [ARCHIVE] on Nostr: 📅 Original date posted:2022-07-11 📝 Original message:On Sun, Jul 10, 2022 at ...
📅 Original date posted:2022-07-11
📝 Original message:On Sun, Jul 10, 2022 at 3:05 AM vjudeu via bitcoin-dev
<bitcoin-dev at 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
Published at
2023-06-07 23:11:32Event JSON
{
"id": "5b16da7fc5206fae982df65b2801ffea7ca8f06a73126d5b6cce1e3a76ae3571",
"pubkey": "49b53f26ac99ee5bae2bf643509aad3199c05af08cbf1fc3030bf11d149c9273",
"created_at": 1686179492,
"kind": 1,
"tags": [
[
"e",
"58ba5412c6c2b5602710ac2f4e1819c2f92facaa3c9fa557b2ad25c78b5dd662",
"",
"root"
],
[
"e",
"99fba4264dd78f4c1e97cb99bb7c3a0c43ef364a1052a4aff9e04ae5bcacfbf8",
"",
"reply"
],
[
"p",
"8d3cf7eba921036409f1fec074cf8cfd8925bc7cb18e35d358b1ccc89752ee32"
]
],
"content": "📅 Original date posted:2022-07-11\n📝 Original message:On Sun, Jul 10, 2022 at 3:05 AM vjudeu via bitcoin-dev\n\u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e\n\u003e Not really, because people that run full nodes, just accepted Segwit\n\u003e and Taproot. They had no choice. And in case of zero satoshis, it could\n\u003e be the same: you would see zero if you look at raw bytes, but you will\n\u003e see non-zero values, if you use some upgraded client, that will support\n\u003e amount hiding, or other features.\n\u003e\n\u003e Segwit: old nodes see no new signatures, new nodes see all signatures\n\u003e Zero satoshis: old nodes see new zero amounts, new nodes see all amounts\n\u003e\n\u003e It is that simple.\n\nI see what you mean, have the P2P messages depend on whether the peer\nis running old code (doesn't know about tail emission) or new code\n(does know about it).\n\nI don't think this can work in this case. It worked for Segwit because\nthe P2P differences involved only signatures (which determine whether\nthe transaction is valid), not the *effect* of the transaction, that is,\nhow it changes the UTXO set. Consensus requires all nodes to always\nagree on the UTXO set.\n\nLarry Ruane",
"sig": "c601695d0e57213f89765c91ffc694bb821802c732ce34bf2b86cc29bacb90e2c9c7f3963ff46df3d223ca8e3f88d659c74e28b9667f4ee9529ca5a273c0d1e8"
}