Return-Path: Received: from smtp1.osuosl.org (smtp1.osuosl.org [IPv6:2605:bc80:3010::138]) by lists.linuxfoundation.org (Postfix) with ESMTP id 3A1E9C000E for ; Tue, 29 Jun 2021 22:22:54 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id 21CE782438 for ; Tue, 29 Jun 2021 22:22:54 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -0.001 X-Spam-Level: X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, 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: smtp1.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=lifewithalacrity-com.20150623.gappssmtp.com Received: from smtp1.osuosl.org ([127.0.0.1]) by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AQ-JiXDyHPEz for ; Tue, 29 Jun 2021 22:22:52 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 Received: from mail-vk1-xa2e.google.com (mail-vk1-xa2e.google.com [IPv6:2607:f8b0:4864:20::a2e]) by smtp1.osuosl.org (Postfix) with ESMTPS id BFE3882428 for ; Tue, 29 Jun 2021 22:22:52 +0000 (UTC) Received: by mail-vk1-xa2e.google.com with SMTP id s194so1270vka.5 for ; Tue, 29 Jun 2021 15:22:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lifewithalacrity-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=kYs+d72dPPUjATJro/Y4pomy1Hq1TOxRxAXufIiPrzo=; b=qJ+bTEYG0DDGF6IYu7ke0TG6UA+Mk09peNfaAAx+kTyTsPMJKsmomG0nMyA12YxYnT iPtGmuK360peSxqgvCEKzmSK4cyDf+rAN/p1czY8Db/i4wgWPn1e3ihHxRqXNOwEB34E eRK91nmThAhOQaPeVbQlHPXyy5jK0a79Qa2et4MJWixr9gPAdn+1p/YHfaom7oVP0s8A ObGcbxUioJhHBOsvUitCmWqiAk6YERIxpw5zte4wJPscpZU74cJGamwkIJ4ip9rdjFig iAt3mljcrA9N+jUBtklt0dwK09HzM2lvLqz/m4doPchr6K5Y38oVfqSKOJQNy0FgUxmb C5jQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=kYs+d72dPPUjATJro/Y4pomy1Hq1TOxRxAXufIiPrzo=; b=TUTnLrfRVkvF/lU5tH/n+EzDTCjd4Y0QlUYzl/qBBFu6XgPCcei7zUQCpOGjkAXg1j sTJHOvsuIstKdwWUjG4XjwFY020LnhO2MhzgDItzvB7ogI0Kf+4+l9NZABwCQbq+kVub EeeaTPzQtgq4Q0zYL2sHpkp0Ix5ettTuHw+AJCpc/q5Ta1K4E/jYMV/YtE2Mv6lRxem+ Y0WFp3P600Iycp87vmGMetzOsbOoCcr4Q+pVbzoD+DujGQBBbJCdMgdjIgDhVZQg7o5u fS3FY6FbBrXo4Hhs1Ch9ieYlmnYtQ4aeIWV1zv08zhUxDA8T5J8cleAuVCypTzzrSLH/ Bqww== X-Gm-Message-State: AOAM531HaFKhlB6sXdB7uYHPP6Gx7LIqjPYEilXvLW7t2BXp37dmysHy Q07gdu8EoQaa6uu9v7/OAMIQV4QYpuj47lNLPeoCANnqNuQ= X-Google-Smtp-Source: ABdhPJzKfmFa5HGbIGAb0JMIYK3Omm3pwh8VphdLOvKqvyvh8pc69gGjFCqMOGPjn5JHK4nVnl9qPQQC4js0bv52ffQ= X-Received: by 2002:ac5:cfc1:: with SMTP id m1mr11423426vkf.13.1625005371492; Tue, 29 Jun 2021 15:22:51 -0700 (PDT) MIME-Version: 1.0 References: <1eb7b635-094c-a583-7dc0-21cea58ed1fb@achow101.com> In-Reply-To: <1eb7b635-094c-a583-7dc0-21cea58ed1fb@achow101.com> From: Christopher Allen Date: Tue, 29 Jun 2021 18:22:39 -0400 Message-ID: To: Andrew Chow , Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="000000000000ed0fef05c5ef0b32" X-Mailman-Approved-At: Tue, 29 Jun 2021 22:41:25 +0000 Subject: Re: [bitcoin-dev] BIP Proposals for Output Script Descriptors 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: Tue, 29 Jun 2021 22:22:54 -0000 --000000000000ed0fef05c5ef0b32 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Are there any plans other than `raw` to support time locks in descriptors? Any plans for descriptors offering closer integration with miniscript? All of Blockchain Commons libraries and tools are multisig descriptor centric, and there are many scenarios that require describing time locks: - [Designing Multisig for Independence & Resilience]( https://github.com/BlockchainCommons/Gordian/blob/master/Docs/Multisig.m= d ) =E2=80=94 Christopher Allen --000000000000ed0fef05c5ef0b32 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Are there any plans other than `raw` to support time lock= s in descriptors?

Any pl= ans for descriptors offering closer integration with miniscript?

All of Blockchain Commons librarie= s and tools are multisig descriptor centric, and there are many scenarios t= hat require describing time locks:=C2=A0
=E2=80=94 Christopher= Allen
--000000000000ed0fef05c5ef0b32--