diff options
author | Rijndael <rot13maxi@protonmail.com> | 2022-11-26 00:12:10 +0000 |
---|---|---|
committer | bitcoindev <bitcoindev@gnusha.org> | 2022-11-26 00:12:26 +0000 |
commit | c992a8e65ece1983b599e689db89eca8ac678585 (patch) | |
tree | 5bcdead60e842c15e83bf3b45d03cd3c7c2535c9 | |
parent | 76820c0abbff916d9ac4a71915213a4dc998db0e (diff) | |
download | pi-bitcoindev-c992a8e65ece1983b599e689db89eca8ac678585.tar.gz pi-bitcoindev-c992a8e65ece1983b599e689db89eca8ac678585.zip |
Re: [bitcoin-dev] Relative txout amounts with a Merkleized Sum Tree and explicit miner fee.
-rw-r--r-- | 21/bde1e5275c34f727a8e57ed0f9599b70e0cdcb | 126 |
1 files changed, 126 insertions, 0 deletions
diff --git a/21/bde1e5275c34f727a8e57ed0f9599b70e0cdcb b/21/bde1e5275c34f727a8e57ed0f9599b70e0cdcb new file mode 100644 index 000000000..01e130cf6 --- /dev/null +++ b/21/bde1e5275c34f727a8e57ed0f9599b70e0cdcb @@ -0,0 +1,126 @@ +Return-Path: <rot13maxi@protonmail.com> +Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133]) + by lists.linuxfoundation.org (Postfix) with ESMTP id 75F80C002D + for <bitcoin-dev@lists.linuxfoundation.org>; + Sat, 26 Nov 2022 00:12:26 +0000 (UTC) +Received: from localhost (localhost [127.0.0.1]) + by smtp2.osuosl.org (Postfix) with ESMTP id 43FEC405B0 + for <bitcoin-dev@lists.linuxfoundation.org>; + Sat, 26 Nov 2022 00:12:26 +0000 (UTC) +DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 43FEC405B0 +Authentication-Results: smtp2.osuosl.org; + dkim=pass (2048-bit key) header.d=protonmail.com header.i=@protonmail.com + header.a=rsa-sha256 header.s=protonmail3 header.b=hkO4nvY9 +X-Virus-Scanned: amavisd-new at osuosl.org +X-Spam-Flag: NO +X-Spam-Score: -0.203 +X-Spam-Level: +X-Spam-Status: No, score=-0.203 tagged_above=-999 required=5 + tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, + DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, + RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] + autolearn=ham autolearn_force=no +Received: from smtp2.osuosl.org ([127.0.0.1]) + by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) + with ESMTP id FPLt0TKlH6pS + for <bitcoin-dev@lists.linuxfoundation.org>; + Sat, 26 Nov 2022 00:12:25 +0000 (UTC) +X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0 +DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org D16D14010F +Received: from mail-40131.protonmail.ch (mail-40131.protonmail.ch + [185.70.40.131]) + by smtp2.osuosl.org (Postfix) with ESMTPS id D16D14010F + for <bitcoin-dev@lists.linuxfoundation.org>; + Sat, 26 Nov 2022 00:12:24 +0000 (UTC) +Date: Sat, 26 Nov 2022 00:12:10 +0000 +DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; + s=protonmail3; t=1669421542; x=1669680742; + bh=0US996hwYQRhQV/3u6AIVxcs4uBh2cW2cQmdaFYUtsg=; + h=Date:To:From:Subject:Message-ID:In-Reply-To:References: + Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: + Message-ID:BIMI-Selector; + b=hkO4nvY9BpstOECqOAvtz/KBd+o7LG2iOqzK7p6kAPISD/n8OjxlgVI0c/ithjyzB + rm/WVFyK6NxS7PHiDABA/3KmBX6vU20ktFAPj5aLJt3kOMJLkHpVqYMZ5R8gIwsyqn + dJbadmDv56vFoJkzWThGgh4DP+lj7ElbDgGDOzLT9nAnzqzKPNxIQc5s0Ut95XloO0 + PFIRPyDYZvYvdMFlum+boTgsEgAuD+mamiYxGyJ2A8mKrlFRg6Yo3a53vsAzYVH6qc + CZNRyfsNoxDkIVwT6zZbiszNtxDUZZ6h82wdMrQ40cwyRQvVoKwu/QiJhQMVEQAamY + jExGdYtn6UyCg== +To: ZmnSCPxj <ZmnSCPxj@protonmail.com>, + Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>, + Andrew Melnychuk Oseen <amo.personal@protonmail.com> +From: Rijndael <rot13maxi@protonmail.com> +Message-ID: <5ded6a45-9e79-511b-f1db-384168102890@protonmail.com> +In-Reply-To: <Kcqi_Svol1F4H8rGnnECZXRkb5Aa_763DlNUP4froIqLovFk-SrOnWXC5ZPtfRjzHb55_BTe07h6PH5OdaY2zpNPNTix__bqYiBIEw2IbjA=@protonmail.com> +References: <zKbMpqEqH6Z4p1GE2rlsOky1fMPBsEFGaeNk8WIcbez__-fR3ahnYEWOgExHC8KXAYCqtt4gMa7WBXkNSqL6fO9sjsvyu9AZRPQIQADqthg=@protonmail.com> + <Kcqi_Svol1F4H8rGnnECZXRkb5Aa_763DlNUP4froIqLovFk-SrOnWXC5ZPtfRjzHb55_BTe07h6PH5OdaY2zpNPNTix__bqYiBIEw2IbjA=@protonmail.com> +Feedback-ID: 41648937:user:proton +MIME-Version: 1.0 +Content-Type: text/plain; charset=utf-8 +Content-Transfer-Encoding: quoted-printable +X-Mailman-Approved-At: Sat, 26 Nov 2022 00:14:17 +0000 +Subject: Re: [bitcoin-dev] Relative txout amounts with a Merkleized Sum Tree + and explicit miner fee. +X-BeenThere: bitcoin-dev@lists.linuxfoundation.org +X-Mailman-Version: 2.1.15 +Precedence: list +List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org> +List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, + <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe> +List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/> +List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org> +List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help> +List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, + <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe> +X-List-Received-Date: Sat, 26 Nov 2022 00:12:26 -0000 + +Hello Andrew, + +As ZmnSCPxj mentioned, covenant schemes are probably something that you +should be looking at and thinking about. In addition to CTV, I'd also +recommend you take a look (if you haven't already) at +`TAPLEAF_UPDATE_VERIFY` +(https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-September/019= +419.html). + From your description, it sounds like you may be barking up a similar tree= +. + +Rijndael + + +On 11/21/22 6:52 PM, ZmnSCPxj via bitcoin-dev wrote: +> Good morning Andrew, +> +>> +>> Can output amounts be mapped to a tap branch? For the goal of secure par= +tial spends of a single UTXO? Looking for feedback on this idea. I got it f= +rom Taro. +> +> Not at all. +> +> The issue you are facing here is that only one tap branch will ever consu= +me the entire input amount. +> That is: while Taproot has multiple leaves, only exactly one leaf will ev= +er be published onchain and that gets the whole amount. +> +> What you want is multiple tree leaves where ALL of them will EVENTUALLY b= +e published, just not right now. +> +> In that case, look at the tree structures for `OP_CHECKTEMPLATEVERIFY`, w= +hich are exactly what you are looking for, and help make `OP_CTV` a reality= +. +> +> Without `OP_CHECKTEMPLATEVERIFY` it is possible to use presigned transact= +ions in a tree structure to do this same construction. +> Presigned transactions are known to be larger than `OP_CHECKTEMPLATEVERIF= +Y` --- signatures on taproot are 64 bytes of witness, but an `OP_CHECKTEMPL= +ATEVERIFY` in a P2WSH reveals just 32 bytes of witness plus the `OP_CHECKTE= +MPLATEVERIFY` opcode. +> +> Regards, +> ZmnSCPxj +> _______________________________________________ +> bitcoin-dev mailing list +> bitcoin-dev@lists.linuxfoundation.org +> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev + + |