📅 Original date posted:2021-08-05
📝 Original message:On Thu, Aug 5, 2021 at 8:07 AM Sjors Provoost via bitcoin-dev <
bitcoin-dev at 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20210805/9bc986ff/attachment.html>;
Christopher Allen [ARCHIVE] /
npub19g…ct5d0
2023-06-07 22:57:44
in reply to nevent1q…a4au
Author Public Key
npub19g47w5ewcqlpd7n07wpkp5cvcu2gjwrse0vl47l0avwl9hu933xsqct5d0Published at
2023-06-07 22:57:44Event JSON
{
"id": "f90ef4f87910a58584708b7d0ada4a5410b3242bb05a6acb2df6e5ec392341d9",
"pubkey": "2a2be7532ec03e16fa6ff38360d30cc714893870cbd9fafbefeb1df2df858c4d",
"created_at": 1686178664,
"kind": 1,
"tags": [
[
"e",
"8e89042ac0c5e548313c6948fd41082d39967acc2858d23ee830ad18f805774c",
"",
"root"
],
[
"e",
"4ac2e3268a8ac48748fe29039d87a3ce8b1d44f397867a444fbf5c835e54d4d8",
"",
"reply"
],
[
"p",
"e1ad0d0d83103f222425541294008149d215c1e1629b0bb37b98e19f698feb3e"
]
],
"content": "📅 Original date posted:2021-08-05\n📝 Original message:On Thu, Aug 5, 2021 at 8:07 AM Sjors Provoost via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e One thing on my wish list - for this BIP, BIP 88 (Hierarchical\n\u003e Deterministic Path Templates) or yet another one - is to include a birth\n\u003e date (minimum block height). E.g. tr([m/86'/0'/0']xpub.../{0-1}/*)\u003e709631\n\u003e\n\u003e And then of course there's the gap limit. Perhaps we just need a\n\u003e \"metadata\" format to go along with descriptors to track the birth data, gap\n\u003e limit and anything else you need (nonce collection for musig2 setup?). E.g.\n\u003e a simple dictionary: tr([m/86'/0'/0']xpub.../{0-1}/*){dob:709631,gap:1000}\n\u003e\n\nThe UR standards we use in Airgap Wallet Community for interoperability\n(currently used by a number of recent wallets for airgap PSBT via animated\nQR) leverages CBOR's tagging capability, and thus explicitly supports\nmetadata. In particular the spec reference code support optional seed\nbirthdate as some wallet vendors really wanted that metadata.\n\nIt would be trivial to support it for hd-keys, and if gap is important, we\ncould also easily add this to the hd-keys spec as well. That is part of the\nreason why use CBOR for the underlying binary encoding is tagging lets\nus add important metadata. The UR standards themselves adds to binary CBOR\nencoding a very efficient transport via QRs or URLs that leverage native QR\ncompression.\n\nSee:\n* Video: [Blockchain Commons Technology Overview](\nhttps://www.youtube.com/watch?v=RYgOFSdUqWY)\n* Articles: [URs: An Overview](Docs/ur-1-overview.md)\n * [A Guide to Using URs for Key Material](Docs/ur-2-keys.md)\n *[A Guide to Using URs for SSKRs](Docs/ur-3-sskrs.md)**\n * [A Guide to Using UR Request \u0026 Response](Docs/ur-99-request-response.md)\n* Specs:\n * [Research 2020-05 - Uniform Resources (UR): Encoding Structured Binary\nData for Transport in URIs and QR Codes](\nhttps://github.com/BlockchainCommons/Research/blob/master/papers/bcr-2020-005-ur.md\n)\n * [Reserach 2020 - UR Type Definition for Hierarchical Deterministic (HD)\nKeys](\nhttps://github.com/BlockchainCommons/Research/blob/master/papers/bcr-2020-007-hdkey.md\n)\n\nIf you have questions about these, drop by the Airgapped Wallet Community\non GitHub at https://github.com/BlockchainCommons/Airgapped-Wallet-Community\n\n-- Christopher Allen\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20210805/9bc986ff/attachment.html\u003e",
"sig": "0a2ca81c59c23fb812a8ba2920fd0dc439daaf3b4522e54a9a7a3826f888aa869621dd63a260e625c6d37852c53b3f38d647de4f3f5321aba39adc4652fdab05"
}