Return-Path: Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136]) by lists.linuxfoundation.org (Postfix) with ESMTP id 7A5B3C0029 for ; Sat, 3 Jun 2023 08:07:17 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp3.osuosl.org (Postfix) with ESMTP id 4E36C60B9E for ; Sat, 3 Jun 2023 08:07:17 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 4E36C60B9E Authentication-Results: smtp3.osuosl.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20221208 header.b=ITpyqPRs X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=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 3Zxn4DsxmMDz for ; Sat, 3 Jun 2023 08:07:15 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org A91F460B53 Received: from mail-ej1-x635.google.com (mail-ej1-x635.google.com [IPv6:2a00:1450:4864:20::635]) by smtp3.osuosl.org (Postfix) with ESMTPS id A91F460B53 for ; Sat, 3 Jun 2023 08:07:15 +0000 (UTC) Received: by mail-ej1-x635.google.com with SMTP id a640c23a62f3a-973f8dbcc02so455048366b.3 for ; Sat, 03 Jun 2023 01:07:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1685779634; x=1688371634; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=PMqLH8SejUdhMQoB5y9oWZTA+ep+BFX4DniPsRNnEUs=; b=ITpyqPRssIv6EuXSKdFFkMlpn+VG6NkoMibR5o8s7f8cIvFgMlMWD42HJdkVwwqm1L tfHzIgRBch4/u0QVsnNTWq5hbOuEdfwy1rSdrcCmK7SBAwhcSH3TjTpQIYq8uT5LVC0p 8TpXddhuHGvhZAdlzydjT7C7qhEvpRQm7thQZYKzzao0RnCMtUeSc/sMqrDLB/ZYGx9v vrscINiAFiUGHRj1JLjde7ohnv5rhCDoS9gwvyxr7h8CkRlH6siAn6EqvGxTau+hw+og ADO7tPDw61xiwBARLufHY1TwT+tcKZD/6vBPhXAWLqGOv/h/hAXQrgl6WuOxmhvwIZWn OIIg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685779634; x=1688371634; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=PMqLH8SejUdhMQoB5y9oWZTA+ep+BFX4DniPsRNnEUs=; b=ZTYeB/THRLhXaNYtCwIoX/MbKmZu6OcnLeFe68/mPZJy4vC3xafe5pg+bcMSuvvulP 25N9XiXhsy4gqqkDxdxpLY53PI9cDyiv2bYAMR7kLGSMwaH4MgvDcgq0+zK3KQOIQ6Af g0hR9JiBV+T3pGomLQ9u1HZxZqnlirm7w4TGsAXSw/zMtMU9FUNALzg1VvvvMAWM55CI bkUGawuiadG0Q5XREGsBQfoVAsnjYv/ZZWhIISF13qf8W+m9X6/KK7d12Y112639xIoi rObT/IYN36dlKqoMqe3jeTmjQ41rku7CTrtZYW5Ii4JW75/YM6uGRPm9HKMRIUGRT0Rv 2fPw== X-Gm-Message-State: AC+VfDzEMviXv/yAtm4B+Ntz8jfW+uFHryBcFTT5xwnPpJVVJFj3UmQJ tRkKwD0jdzM3G61XOb7okml4UfKxgTAUVvomFlU= X-Google-Smtp-Source: ACHHUZ7UibV3sKYtuKlQpEXOTJPUlv5uNkBTzSLPXdKTb9DPBG8YPln9dGlMvB8VkVOxSquclwNIBFyp5lRib9H3yGE= X-Received: by 2002:a17:907:3f9f:b0:965:ff38:2fbb with SMTP id hr31-20020a1709073f9f00b00965ff382fbbmr1111077ejc.1.1685779633693; Sat, 03 Jun 2023 01:07:13 -0700 (PDT) MIME-Version: 1.0 References: <29ff546a6007cec1a0f85b91541f8e4d@dtrt.org> In-Reply-To: From: Joost Jager Date: Sat, 3 Jun 2023 10:06:37 +0200 Message-ID: To: "David A. Harding" Content-Type: multipart/alternative; boundary="0000000000003c693105fd3528af" X-Mailman-Approved-At: Sat, 03 Jun 2023 11:30:48 +0000 Cc: Bitcoin Protocol Discussion Subject: Re: [bitcoin-dev] Standardisation of an unstructured taproot annex 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: Sat, 03 Jun 2023 08:07:17 -0000 --0000000000003c693105fd3528af Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Jun 3, 2023 at 9:49=E2=80=AFAM Joost Jager = wrote: > The removal of the need for a commitment transaction also enables the > inclusion of data within a single transaction that relies on its own > transaction identifier (txid). This is possible because the txid > calculation does not incorporate the annex, where the data would be house= d. > This feature can be beneficial in scenarios that require the emulation of > covenants through the use of presigned transactions involving an ephemera= l > signer. > I think this avoidance of a circular reference is also why LN-Symmetry uses the annex? Joost --0000000000003c693105fd3528af Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sat, Jun 3, 2023 at 9:49=E2=80=AFAM Jo= ost Jager <joost.jager@gmail.co= m> wrote:
The removal of the need f= or a commitment transaction also enables the inclusion of data within a sin= gle transaction that relies on its own transaction identifier (txid). This = is possible because the txid calculation does not incorporate the annex, wh= ere the data would be housed. This feature can be beneficial in scenarios t= hat require the emulation of covenants through the use of presigned transac= tions involving an ephemeral signer.

I think this avoidance of a circular reference is also why LN-Symmetr= y uses the annex?

Joost
--0000000000003c693105fd3528af--