On Thu, Aug 5, 2021 at 8:07 AM Sjors Provoost via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> One thing on my wish list - for this BIP, BIP 88 (Hierarchical
> Deterministic Path Templates) or yet another one - is to include a birth
> date (minimum block height). E.g.
Thanks for writing this up!
I think your modular BIP approach makes sense. (the abstract should mention
this too)
Contents look good to me, modulo missing test vectors. I also suggest dropping
combo(), see below.
Regarding the use of h vs ', especially since they result in a different
PO BOX 187, Sangerville, ME 04479 USA
TEL: 207-876-3541 FAX: 207-876-3566
From: "Craig Raw via bitcoin-dev"
To: "David A. Harding"
Cc: "Bitcoin Protocol Discussion"
Sent: Saturday, July 3, 2021 10:00:51 AM
Subject: Re: [bitcoin-dev] BIP Proposals fo
It's a consideration, not a serious concern.
When I made the point around alphanumeric characters being similar to the
path numbers, I was actually thinking of the output descriptor appearing in
a fixed character width font, which I prefer as more appropriate for
displaying hexidecimal values. In
There is a downside to using "h"/"H" from a UX perspective - taking up more
space and appearing as alphanumeric characters similar to the path numbers,
they make derivation paths and descriptors more difficult to read. Also,
although not as important, less efficient when making metal backups.
On
On Sat, Jul 03, 2021 at 10:35:48AM +0200, Craig Raw wrote:
> There is a downside to using "h"/"H" from a UX perspective - taking up more
> space
Is this a serious concern of yours? An apostrophe is 1/2 en; an "h" is
1 en; the following descriptor contains three hardened derivations in 149
On 7/2/21 11:24 PM, David A. Harding wrote:
> Is there any chance we can take this opportunity to make "h"/"H" the
> preferred aliases? Using "'" in bourne-style shells is very
> annoying[1], and I suspect it's also creating unnecessary complications
> elsewhere.
I've updated the text to use "h".
On Tue, Jun 29, 2021 at 09:14:39PM +, Andrew Chow via bitcoin-dev wrote:
> *** Optionally followed by a single /* or /*' final
> step to denote all direct unhardened or hardened children.
>
> [...]
>
> In the above specification, the hardened indicator ' may be
> replaced with alternative
I've opened a PR against my own BIPs fork for review:
https://github.com/achow101/bips/pull/3
Andrew
On 6/29/21 11:41 PM, Jeremy wrote:
> Kudos, this is fantastic!
>
> It might be easier, since there is a ton of content here, for you to open up
> some WIP PRs to collect feedback?
> --
>
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:
-
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
Hi All,
I've been working on formalizing the Output Script Descriptors that have
been available in Bitcoin Core for a while into BIPs. Since descriptors
are modular and have optional components, I've decided to split it into
7 BIPs, rather than a single one. The first describes descriptors in
12 matches
Mail list logo
