From: Christopher Allen <ChristopherA@lifewithalacrity•com>
To: Sjors Provoost <sjors@sprovoost•nl>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP Proposals for Output Script Descriptors
Date: Thu, 5 Aug 2021 13:49:43 -0700 [thread overview]
Message-ID: <CACrqygAVreg0ALPeg50vrHB+J=X6quUaEyGv9ia5WgDQzDL10A@mail.gmail.com> (raw)
In-Reply-To: <38AE919F-7EA2-4CF4-9AF8-7E38C7542C59@sprovoost.nl>
[-- Attachment #1: Type: text/plain, Size: 2280 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 3170 bytes --]
prev parent reply other threads:[~2021-08-05 20:50 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
[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 [this message]
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='CACrqygAVreg0ALPeg50vrHB+J=X6quUaEyGv9ia5WgDQzDL10A@mail.gmail.com' \
--to=christophera@lifewithalacrity$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=sjors@sprovoost$(echo .)nl \
/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