Return-Path: Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137]) by lists.linuxfoundation.org (Postfix) with ESMTP id 252C8C002D for ; Mon, 25 Apr 2022 01:46:39 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp4.osuosl.org (Postfix) with ESMTP id F352A40985 for ; Mon, 25 Apr 2022 01:46:38 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -1.398 X-Spam-Level: X-Spam-Status: No, score=-1.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: smtp4.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=q32-com.20210112.gappssmtp.com Received: from smtp4.osuosl.org ([127.0.0.1]) by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XOAx1UcNivGR for ; Mon, 25 Apr 2022 01:46:36 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) by smtp4.osuosl.org (Postfix) with ESMTPS id 60D7D40987 for ; Mon, 25 Apr 2022 01:46:36 +0000 (UTC) Received: by mail-lf1-x12b.google.com with SMTP id bu29so23735070lfb.0 for ; Sun, 24 Apr 2022 18:46:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=q32-com.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=efzNmMVqz+thhQYUbAFBg8Yat63epY1Y46rNMADXTAU=; b=UK8NweY/xNqfn3ZvMjlFrHMqeKF+DJw2X92xo6KsoSzoU4+rL0fNt38ork+QZXawZF err3c9rcvsGx9i31ev6mz2mgzGm1asOVw33zl/ExRHw9WnYMPYX/NZPXfN9RJcOJE7qr Xwb1my48cnsLr7leMN3P1zjYZhzzYmuAlqQpfe3sSUZ6cTsWQ1pRPePCZjS6aZQ063yh t0at9zwMxHX+vcFkXDHqRTOAzWhta092vHQkAQ/nYSgwU42TKv5ZuFraOsuhUspKUPFM DeVUQFOsPaYwJWo1yP6oy4qLlH5VqpiTzVadBY0uCKu5Wim3D/AYf+FDgL/23zcMMTOX LghQ== 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=efzNmMVqz+thhQYUbAFBg8Yat63epY1Y46rNMADXTAU=; b=cvYvw/S/GujEb+IrfuyUUFRhoXUrhVeKeUpa88PTocMAsMQiI1m9dKh/KUSWyuNaTL EFJp9XAkxRJttfo0eV9zmELefPzNwQ6G3QMS16fPifUkG5jNPtFaWBQ8cOYNWRbc0fxZ k9ZefHY2onYsiC/R0smvWBTIaP3rFoj4sFNKtqdTOTidWmn9cHR+EVfUVgq4cG19KdaG 4cewKYMEP7HOaKf9s3lo8BfygSlUiLbl4/N72zpXNBJL/RD5DwkTxt4jTV5MM/97cQft l8AUo5ISxI88ksu2GYqafO7Xv0xQZAPPkwAKPg8RSY6Txv3k8/hCrItdfFTuaBJO8Hwi Jy7w== X-Gm-Message-State: AOAM531G5GVyneuGmqXt5ra6exBNx7szRBOnlcsF7Mo46stWqbguOfb5 7ekuLV7aWij4XKx6Kzk2I0xp8BlG0+AnKYHZ37oYV1Q= X-Google-Smtp-Source: ABdhPJzxkP8ptTzrnb2PkqvgsNrEqDIrZVY3jm6ZaicQYNdiaeMclL0aZe3cz9DzFPpKr9tulrKCUca6W4D1MaNyEWE= X-Received: by 2002:a05:6512:22c8:b0:471:a3dd:9e3b with SMTP id g8-20020a05651222c800b00471a3dd9e3bmr11529080lfu.308.1650851194259; Sun, 24 Apr 2022 18:46:34 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Erik Aronesty Date: Sun, 24 Apr 2022 21:46:25 -0400 Message-ID: To: darosior , Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="00000000000002cce905dd70bf18" X-Mailman-Approved-At: Mon, 25 Apr 2022 10:36:12 +0000 Subject: Re: [bitcoin-dev] ANYPREVOUT in place of CTV 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, 25 Apr 2022 01:46:39 -0000 --00000000000002cce905dd70bf18 Content-Type: text/plain; charset="UTF-8" > > > useful!), using APO-AS covers it. And it's not a couple dozen more virtual > bytes that are going to matter for > a potential vault user. > makes sense that byte-efficiency would be likely less important to vault users vs lightning noninteractive channel users > > the meantime others will have been able to deploy new applications > leveraging ANYPREVOUT (Eltoo, blind > statechains, etc..[1]). > a smaller code change that seems much less controversial --00000000000002cce905dd70bf18 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

useful!), using APO-AS covers it. And it's not a= couple dozen more virtual bytes that are going to matter for
a potential vault user.

makes sense tha= t byte-efficiency would be likely less important to vault users vs lightnin= g noninteractive channel users
=C2=A0

the meantime others will have been able to deploy new applications leve= raging ANYPREVOUT (Eltoo, blind
statechains, etc..[1]).

a smaller code = change that seems much less controversial

--00000000000002cce905dd70bf18--