MIME-Version: 1.0
References: <1eb7b635-094c-a583-7dc0-21cea58ed1fb@achow101.com>
 <38AE919F-7EA2-4CF4-9AF8-7E38C7542C59@sprovoost.nl>
In-Reply-To: <38AE919F-7EA2-4CF4-9AF8-7E38C7542C59@sprovoost.nl>
From: Christopher Allen <ChristopherA@lifewithalacrity.com>
Date: Thu, 5 Aug 2021 13:49:43 -0700
Message-ID: <CACrqygAVreg0ALPeg50vrHB+J=X6quUaEyGv9ia5WgDQzDL10A@mail.gmail.com>
To: Sjors Provoost <sjors@sprovoost.nl>, 
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="0000000000002c459205c8d611fa"
Subject: Re: [bitcoin-dev] BIP Proposals for Output Script Descriptors
Precedence: list

--0000000000002c459205c8d611fa
Content-Type: text/plain; charset="UTF-8"

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. tr([m/86'/0'/0']xpub.../{0-1}/*)>709631
>
> And then of course there's the gap limit. Perhaps we just need a
> "metadata" format to go along with descriptors to track the birth data, gap
> limit and anything else you need (nonce collection for musig2 setup?). E.g.
> a simple dictionary: tr([m/86'/0'/0']xpub.../{0-1}/*){dob:709631,gap:1000}
>

The UR standards we use in Airgap Wallet Community for interoperability
(currently used by a number of recent wallets for airgap PSBT via animated
QR) leverages CBOR's tagging capability, and thus explicitly supports
metadata. In particular the spec reference code support optional seed
birthdate as some wallet vendors really wanted that metadata.

It would be trivial to support it for hd-keys, and if gap is important, we
could also easily add this to the hd-keys spec as well. That is part of the
reason why use CBOR for the underlying binary encoding is tagging lets
us add important metadata. The UR standards themselves adds to binary CBOR
encoding a very efficient transport via QRs or URLs that leverage native QR
compression.

See:
* Video: [Blockchain Commons Technology Overview](
https://www.youtube.com/watch?v=RYgOFSdUqWY)
* Articles: [URs: An Overview](Docs/ur-1-overview.md)
  * [A Guide to Using URs for Key Material](Docs/ur-2-keys.md)
  *[A Guide to Using URs for SSKRs](Docs/ur-3-sskrs.md)**
  * [A Guide to Using UR Request & Response](Docs/ur-99-request-response.md)
* Specs:
  * [Research 2020-05 - Uniform Resources (UR): Encoding Structured Binary
Data for Transport in URIs and QR Codes](
https://github.com/BlockchainCommons/Research/blob/master/papers/bcr-2020-005-ur.md
)
  * [Reserach 2020 - UR Type Definition for Hierarchical Deterministic (HD)
Keys](
https://github.com/BlockchainCommons/Research/blob/master/papers/bcr-2020-007-hdkey.md
)

If you have questions about these, drop by the Airgapped Wallet Community
on GitHub at https://github.com/BlockchainCommons/Airgapped-Wallet-Community

-- Christopher Allen

--0000000000002c459205c8d611fa
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Thu, Aug 5, 2021 at 8:07 AM Sjors Prov=
oost via bitcoin-dev &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundatio=
n.org">bitcoin-dev@lists.linuxfoundation.org</a>&gt; wrote:<br></div><div c=
lass=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-col=
or:rgb(204,204,204);padding-left:1ex">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. tr([m/86&#39;/0&#=
39;/0&#39;]xpub.../{0-1}/*)&gt;709631<br>
<br>
And then of course there&#39;s the gap limit. Perhaps we just need a &quot;=
metadata&quot; format to go along with descriptors to track the birth data,=
 gap limit and anything else you need (nonce collection for musig2 setup?).=
 E.g. a simple dictionary: tr([m/86&#39;/0&#39;/0&#39;]xpub.../{0-1}/*){dob=
:709631,gap:1000}<br></blockquote><div><br></div><div>The UR standards we u=
se in Airgap Wallet Community for interoperability (currently used by a num=
ber of recent wallets for airgap=C2=A0PSBT via animated QR) leverages CBOR&=
#39;s tagging capability, and thus explicitly supports metadata. In particu=
lar the spec reference code=C2=A0support=C2=A0optional seed birthdate as so=
me wallet vendors really wanted that metadata.</div><div><br></div><div>It =
would be trivial=C2=A0to support it for hd-keys, and if gap is important, w=
e could also easily add this to the hd-keys spec as well. That is part of t=
he reason why=C2=A0use CBOR for the underlying binary encoding is tagging l=
ets us=C2=A0add=C2=A0important metadata. The UR standards=C2=A0themselves a=
dds to binary CBOR encoding a very efficient transport via QRs or URLs that=
 leverage native QR compression.</div><div><br></div><div>See:</div><div>* =
Video: [Blockchain Commons Technology Overview](<a href=3D"https://www.yout=
ube.com/watch?v=3DRYgOFSdUqWY">https://www.youtube.com/watch?v=3DRYgOFSdUqW=
Y</a>)</div><div>* Articles: [URs: An Overview](Docs/ur-1-overview.md)<br>=
=C2=A0 * [A Guide to Using URs for Key Material](Docs/ur-2-keys.md)<br>=C2=
=A0 *[A Guide to Using URs for SSKRs](Docs/ur-3-sskrs.md)**<br>=C2=A0 * [A =
Guide to Using UR Request &amp; Response](Docs/ur-99-request-response.md)<b=
r></div><div>* Specs:</div><div>=C2=A0 * [Research 2020-05 - Uniform Resour=
ces (UR): Encoding Structured Binary Data for Transport in URIs and QR Code=
s](<a href=3D"https://github.com/BlockchainCommons/Research/blob/master/pap=
ers/bcr-2020-005-ur.md">https://github.com/BlockchainCommons/Research/blob/=
master/papers/bcr-2020-005-ur.md</a>)</div><div>=C2=A0 * [Reserach 2020 -=
=C2=A0UR Type Definition for Hierarchical Deterministic (HD) Keys](<a href=
=3D"https://github.com/BlockchainCommons/Research/blob/master/papers/bcr-20=
20-007-hdkey.md">https://github.com/BlockchainCommons/Research/blob/master/=
papers/bcr-2020-007-hdkey.md</a>)</div><div><br></div><div>If you have ques=
tions about these, drop by the Airgapped Wallet Community on GitHub at=C2=
=A0<a href=3D"https://github.com/BlockchainCommons/Airgapped-Wallet-Communi=
ty">https://github.com/BlockchainCommons/Airgapped-Wallet-Community</a></di=
v><div><br></div><div>-- Christopher Allen</div></div></div>

--0000000000002c459205c8d611fa--