đź“… Original date posted:2021-08-31
đź“ť Original message:On Tue, Aug 31, 2021 at 12:18 PM Peter D. Gray <peter at coinkite.com> wrote:
> 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.
UR is more than just a QR, it is URL conformant text that is optimized for
compression in QRs.
In particular, take a look at the explanation of the UR format at the 20m0s
mark in this video:
https://youtu.be/RYgOFSdUqWY
The rest of the video explains why we made the choices we did. We wanted to
leverage existing standards, but there were too many compromises expecially
give QR requirements. See the section on “Why Another Standard” in our
overview at
https://github.com/BlockchainCommons/crypto-commons/blob/master/Docs/ur-1-overview.md#why-another-standard
Note that the UR specification just is not just being adopted by wallet
vendors, but also a number of online services / transaction coordinators
that only have access watch-only keys. These services can then do a
crypto-request for the airgapped wallet to sign the PSBT.
— Christopher Allen
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20210831/555ef40b/attachment.html>;
Christopher Allen [ARCHIVE] /
npub19g…ct5d0
2023-06-07 22:58:23
in reply to nevent1q…gsml
Author Public Key
npub19g47w5ewcqlpd7n07wpkp5cvcu2gjwrse0vl47l0avwl9hu933xsqct5d0Published at
2023-06-07 22:58:23Event JSON
{
"id": "4960f6a7e1d8cd697b44f2541cb207ebed730943b6ed0e723cf61418807299ef",
"pubkey": "2a2be7532ec03e16fa6ff38360d30cc714893870cbd9fafbefeb1df2df858c4d",
"created_at": 1686178703,
"kind": 1,
"tags": [
[
"e",
"0102c19bd36d0f378a4cd409e843e7cafde9df6b729698d5a2dd818414f556f0",
"",
"root"
],
[
"e",
"bf9aaa7f72ec717cce15c408deb62750533e014825d5239353dcf0e0d98a2e72",
"",
"reply"
],
[
"p",
"7b004e1cd14bfe95aec539b0a3843c2713d155a939abd807a5714c2a09f484c4"
]
],
"content": "📅 Original date posted:2021-08-31\n📝 Original message:On Tue, Aug 31, 2021 at 12:18 PM Peter D. Gray \u003cpeter at coinkite.com\u003e wrote:\n\n\u003e QR Codes do not use IANA mime-types.\n\u003e\n\u003e If anyone wanted to use UR encoding for PSBT data in a web context (http),\n\u003e NFC, or email, it would probably be best to discourage them.\n\u003e\n\u003e While I can understand the need for UR encoding in animated QR\n\u003e codes, I don't think any other use-case could justify introducing\n\u003e a new word list (ByteWords), a unique checksum algo (Xoshiro256),\n\u003e fountain codes (Luby Transform) and CBOR... just to wrap a few k\n\u003e of binary.\n\u003e\n\u003e I do love CBOR though. It's the best.\n\n\nUR is more than just a QR, it is URL conformant text that is optimized for\ncompression in QRs.\n\nIn particular, take a look at the explanation of the UR format at the 20m0s\nmark in this video:\nhttps://youtu.be/RYgOFSdUqWY\n\nThe rest of the video explains why we made the choices we did. We wanted to\nleverage existing standards, but there were too many compromises expecially\ngive QR requirements. See the section on “Why Another Standard” in our\noverview at\nhttps://github.com/BlockchainCommons/crypto-commons/blob/master/Docs/ur-1-overview.md#why-another-standard\n\nNote that the UR specification just is not just being adopted by wallet\nvendors, but also a number of online services / transaction coordinators\nthat only have access watch-only keys. These services can then do a\ncrypto-request for the airgapped wallet to sign the PSBT.\n\n— Christopher Allen\n\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20210831/555ef40b/attachment.html\u003e",
"sig": "0d049b28b4e35e7439f0e2ff4d0f256d2f81f101531ea81c59478f7229ca76c5c244ff175ec2614b2e4bb8b566214a51fc39f7e03ea694ef05227e1505fa3a55"
}