public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Andrew Chow <achow101-lists@achow101•com>
To: Christopher Allen <ChristopherA@lifewithalacrity•com>,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP Proposals for Output Script Descriptors
Date: Tue, 29 Jun 2021 22:35:49 +0000	[thread overview]
Message-ID: <b8301704-1bec-d7e5-e546-eada63893c7f@achow101.com> (raw)
In-Reply-To: <CACrqygDV3ED7YBJ0tsVuVXomiHTY3iREStn7VZyngM9b-3QDKw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 623 bytes --]

On 6/29/21 6:22 PM, Christopher Allen wrote:

> Are there any plans other than `raw` to support time locks in descriptors?
>
> Any plans for descriptors offering closer integration with miniscript?

I expect miniscript to be a followup BIP that extends these descriptors. Miniscript has timelock functionality.

Andrew

> 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.md)
>
> — Christopher Allen

[-- Attachment #2: Type: text/html, Size: 1819 bytes --]

  reply	other threads:[~2021-06-29 22:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-29 21:14 Andrew Chow
2021-06-29 22:22 ` Christopher Allen
2021-06-29 22:35   ` Andrew Chow [this message]
     [not found] ` <CAD5xwhg9sno+aABgUtiwhBo8mLrmj5m9WowGjnUfv-f1pSbshw@mail.gmail.com>
2021-07-02 20:05   ` Andrew Chow
2021-07-03  3:24 ` David A. Harding
2021-07-03  5:12   ` Andrew Chow
2021-07-03  8:35     ` Craig Raw
2021-07-03 10:05       ` David A. Harding
2021-07-03 14:00         ` Craig Raw
2021-07-04 17:56           ` Daniel Bayerdorffer
2021-08-05 14:27 ` Sjors Provoost
2021-08-05 20:49   ` Christopher Allen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b8301704-1bec-d7e5-e546-eada63893c7f@achow101.com \
    --to=achow101-lists@achow101$(echo .)com \
    --cc=ChristopherA@lifewithalacrity$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox