📅 Original date posted:2021-08-31
📝 Original message:QR Codes do not use IANA mime-types.
If anyone wanted to use UR encoding for PSBT data in a web context (http),
NFC, or email, it would probably be best to discourage them.
While I can understand the need for UR encoding in animated QR
codes, I don't think any other use-case could justify introducing
a new word list (ByteWords), a unique checksum algo (Xoshiro256),
fountain codes (Luby Transform) and CBOR... just to wrap a few k
of binary.
I do love CBOR though. It's the best.
---
@DocHEX || Coinkite || PGP: A3A31BAD 5A2A5B10
On Tue, Aug 31, 2021 at 12:01:23PM -0700, Christopher Allen wrote:
> Note that a number of wallet companies are now supporting the UR encoded
> version of PSBTs, allowing for better QR & Airgap solutions, and also
> leverage CBOR which is an IETF standard.
>
> We have a community of Airgap wallet developers at
> https://github.com/BlockchainCommons/Airgapped-Wallet-Community
>
> …and libraries at
> https://github.com/BlockchainCommons/crypto-commons#urs
>
> We’d love for you to register UR as well, maybe as bitcoin/psbt+ur
>
> Can you bring this up in our community for further discussion?
> https://github.com/BlockchainCommons/Airgapped-Wallet-Community/discussions
>
> Thanks!
>
> — Christopher Allen [via iPhone]
>
> On Tue, Aug 31, 2021 at 11:41 AM Peter D. Gray via bitcoin-dev <
> bitcoin-dev at lists.linuxfoundation.org> wrote:
>
> > Hi list!
> >
> > I am proposing to register the following MIME (RFC 2046) media types with
> > the IANA:
> >
> >
> > bitcoin/psbt
> >
> > - aka. a BIP-174 file, in binary
> > - does not make any claims about signed/unsigned status; lets leave
> > that to the file
> >
> > bitcoin/txn
> >
> > - aka. wire-ready fully-signed transaction in binary
> >
> > bitcoin/uri
> >
> > - aka [BIP-21](
> > https://github.com/bitcoin/bips/blob/master/bip-0021.mediawiki)
> > - could be just a bare bech32 or base58 payment address
> > - but can also encode amount, comments in URL args
> > - potentially interesting as a response to 402 - Payment required
> >
> >
> > Other thoughts
> >
> > - some mime-types are proposed in BIP-71 but those are unrelated to above,
> > and never
> > seem to have been registered
> >
> > - for those who like to encode their binary as base64 or hex, that can be
> > indicated
> > as "encoding=hex" or "encoding=base64" in the optional parameters, just
> > like
> > "text/plain; encoding=utf-8" does. However, the default must be binary.
> >
> > - although the above are useful for web servers, they are also useful
> > elsewhere and I
> > intend to use them in NFC (NDEF records) where a shorter length is
> > critical.
> >
> > - I have no idea how easily IANA will accept these proposals.
> >
> > - current approved mime types:
> > https://www.iana.org/assignments/media-types/media-types.xhtml
> >
> > Thoughts?
> >
> > ---
> > @DocHEX || Coinkite || PGP: A3A31BAD 5A2A5B10
> >
> > _______________________________________________
> > bitcoin-dev mailing list
> > bitcoin-dev at lists.linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> >
Peter D. Gray [ARCHIVE] /
npub10v…t058y
2023-06-07 22:58:23
in reply to nevent1q…r488
Author Public Key
npub10vqyu8x3f0lfttk98xc28ppuyufaz4df8x4aspa9w9xz5z05snzq7t058yPublished at
2023-06-07 22:58:23Event JSON
{
"id": "bf9aaa7f72ec717cce15c408deb62750533e014825d5239353dcf0e0d98a2e72",
"pubkey": "7b004e1cd14bfe95aec539b0a3843c2713d155a939abd807a5714c2a09f484c4",
"created_at": 1686178703,
"kind": 1,
"tags": [
[
"e",
"0102c19bd36d0f378a4cd409e843e7cafde9df6b729698d5a2dd818414f556f0",
"",
"root"
],
[
"e",
"4c9f26ce49e8b8644edb538bd065edfeac836b796138473f20ae10f0c227f616",
"",
"reply"
],
[
"p",
"2a2be7532ec03e16fa6ff38360d30cc714893870cbd9fafbefeb1df2df858c4d"
]
],
"content": "📅 Original date posted:2021-08-31\n📝 Original message:QR Codes do not use IANA mime-types.\n\nIf anyone wanted to use UR encoding for PSBT data in a web context (http),\nNFC, or email, it would probably be best to discourage them.\n\nWhile I can understand the need for UR encoding in animated QR\ncodes, I don't think any other use-case could justify introducing\na new word list (ByteWords), a unique checksum algo (Xoshiro256),\nfountain codes (Luby Transform) and CBOR... just to wrap a few k\nof binary.\n\nI do love CBOR though. It's the best.\n\n---\n@DocHEX || Coinkite || PGP: A3A31BAD 5A2A5B10\n\nOn Tue, Aug 31, 2021 at 12:01:23PM -0700, Christopher Allen wrote:\n\u003e Note that a number of wallet companies are now supporting the UR encoded\n\u003e version of PSBTs, allowing for better QR \u0026 Airgap solutions, and also\n\u003e leverage CBOR which is an IETF standard.\n\u003e \n\u003e We have a community of Airgap wallet developers at\n\u003e https://github.com/BlockchainCommons/Airgapped-Wallet-Community\n\u003e \n\u003e …and libraries at\n\u003e https://github.com/BlockchainCommons/crypto-commons#urs\n\u003e \n\u003e We’d love for you to register UR as well, maybe as bitcoin/psbt+ur\n\u003e \n\u003e Can you bring this up in our community for further discussion?\n\u003e https://github.com/BlockchainCommons/Airgapped-Wallet-Community/discussions\n\u003e \n\u003e Thanks!\n\u003e \n\u003e — Christopher Allen [via iPhone]\n\u003e \n\u003e On Tue, Aug 31, 2021 at 11:41 AM Peter D. Gray via bitcoin-dev \u003c\n\u003e bitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e \n\u003e \u003e Hi list!\n\u003e \u003e\n\u003e \u003e I am proposing to register the following MIME (RFC 2046) media types with\n\u003e \u003e the IANA:\n\u003e \u003e\n\u003e \u003e\n\u003e \u003e bitcoin/psbt\n\u003e \u003e\n\u003e \u003e - aka. a BIP-174 file, in binary\n\u003e \u003e - does not make any claims about signed/unsigned status; lets leave\n\u003e \u003e that to the file\n\u003e \u003e\n\u003e \u003e bitcoin/txn\n\u003e \u003e\n\u003e \u003e - aka. wire-ready fully-signed transaction in binary\n\u003e \u003e\n\u003e \u003e bitcoin/uri\n\u003e \u003e\n\u003e \u003e - aka [BIP-21](\n\u003e \u003e https://github.com/bitcoin/bips/blob/master/bip-0021.mediawiki)\n\u003e \u003e - could be just a bare bech32 or base58 payment address\n\u003e \u003e - but can also encode amount, comments in URL args\n\u003e \u003e - potentially interesting as a response to 402 - Payment required\n\u003e \u003e\n\u003e \u003e\n\u003e \u003e Other thoughts\n\u003e \u003e\n\u003e \u003e - some mime-types are proposed in BIP-71 but those are unrelated to above,\n\u003e \u003e and never\n\u003e \u003e seem to have been registered\n\u003e \u003e\n\u003e \u003e - for those who like to encode their binary as base64 or hex, that can be\n\u003e \u003e indicated\n\u003e \u003e as \"encoding=hex\" or \"encoding=base64\" in the optional parameters, just\n\u003e \u003e like\n\u003e \u003e \"text/plain; encoding=utf-8\" does. However, the default must be binary.\n\u003e \u003e\n\u003e \u003e - although the above are useful for web servers, they are also useful\n\u003e \u003e elsewhere and I\n\u003e \u003e intend to use them in NFC (NDEF records) where a shorter length is\n\u003e \u003e critical.\n\u003e \u003e\n\u003e \u003e - I have no idea how easily IANA will accept these proposals.\n\u003e \u003e\n\u003e \u003e - current approved mime types:\n\u003e \u003e https://www.iana.org/assignments/media-types/media-types.xhtml\n\u003e \u003e\n\u003e \u003e Thoughts?\n\u003e \u003e\n\u003e \u003e ---\n\u003e \u003e @DocHEX || Coinkite || PGP: A3A31BAD 5A2A5B10\n\u003e \u003e\n\u003e \u003e _______________________________________________\n\u003e \u003e bitcoin-dev mailing list\n\u003e \u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e \u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e \u003e",
"sig": "eddea75a26f32557a452b5f78a33c2f56eecba9a10c0ff4e200a3efad97c7535e0076d0a8a05588b3b709efb2d391a26a5d54751e8a499ad5aedba4ea7599a4f"
}