MIME-Version: 1.0
References: <mailman.9346.1630015566.1160.bitcoin-dev@lists.linuxfoundation.org>
 <20210831182741.GV91472@coinkite.com>
 <CACrqygDZGWxrv+3w=gmwVRO4iTLYJnn8QLBEwNQ_EdkXNr46Ww@mail.gmail.com>
 <20210831191800.GW91472@coinkite.com>
In-Reply-To: <20210831191800.GW91472@coinkite.com>
From: Christopher Allen <ChristopherA@lifewithalacrity.com>
Date: Tue, 31 Aug 2021 13:02:44 -0700
Message-ID: <CACrqygABxGBDHf4n68UxbHLg3Ai60c6Z9gcF=-XFc2FyoBSqeg@mail.gmail.com>
To: Peter Gray <peter@coinkite.com>
Content-Type: multipart/alternative; boundary="0000000000007ffa4605cae06f98"
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
 Wolf McNally <wolf@wolfmcnally.com>,
 Shannon Appelcline <shannon.appelcline@gmail.com>
Subject: Re: [bitcoin-dev] Proposal for a few IANA mime-types related to
	Bitcoin
Precedence: list

--0000000000007ffa4605cae06f98
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Aug 31, 2021 at 12:18 PM Peter D. Gray <peter@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 =E2=80=9CWhy Another Standard=E2=
=80=9D in our
overview at
https://github.com/BlockchainCommons/crypto-commons/blob/master/Docs/ur-1-o=
verview.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.

=E2=80=94 Christopher Allen

>

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

<div><br></div><div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=
=3D"gmail_attr">On Tue, Aug 31, 2021 at 12:18 PM Peter D. Gray &lt;<a href=
=3D"mailto:peter@coinkite.com">peter@coinkite.com</a>&gt; wrote:<br></div><=
blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l=
eft-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rg=
b(204,204,204)">QR Codes do not use IANA mime-types.<br>
<br>
If anyone wanted to use UR encoding for PSBT data in a web context (http),<=
br>
NFC, or email, it would probably be best to discourage them.<br>
<br>
While I can understand the need for UR encoding in animated QR<br>
codes, I don&#39;t think any other use-case could justify introducing<br>
a new word list (ByteWords), a unique checksum algo (Xoshiro256),<br>
fountain codes (Luby Transform) and CBOR... just to wrap a few k<br>
of binary.<br>
<br>
I do love CBOR though. It&#39;s the best.</blockquote><div dir=3D"auto"><br=
></div><div dir=3D"auto"><div dir=3D"auto" style=3D"border-color:rgb(0,0,0)=
;color:rgb(0,0,0)">UR is more than just a QR, it is URL conformant text tha=
t is optimized for compression in QRs.=C2=A0</div><div dir=3D"auto" style=
=3D"border-color:rgb(0,0,0);color:rgb(0,0,0)"><br></div><div dir=3D"auto" s=
tyle=3D"border-color:rgb(0,0,0);color:rgb(0,0,0)">In particular, take a loo=
k at the explanation of the UR format at the 20m0s mark in this video:=C2=
=A0<div style=3D"border-color:rgb(0,0,0)"><a href=3D"https://youtu.be/RYgOF=
SdUqWY">https://youtu.be/RYgOFSdUqWY</a></div><div style=3D"border-color:rg=
b(0,0,0)" dir=3D"auto"><br></div><div style=3D"border-color:rgb(0,0,0)" dir=
=3D"auto">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 =E2=80=9CWhy Another S=
tandard=E2=80=9D in our overview at=C2=A0<div><a href=3D"https://github.com=
/BlockchainCommons/crypto-commons/blob/master/Docs/ur-1-overview.md#why-ano=
ther-standard">https://github.com/BlockchainCommons/crypto-commons/blob/mas=
ter/Docs/ur-1-overview.md#why-another-standard</a></div><div dir=3D"auto"><=
br></div><div dir=3D"auto">Note that the UR specification just is not just =
being adopted by wallet vendors, but also a number of online services / tra=
nsaction coordinators that only have access watch-only keys. These services=
 can then do a crypto-request for the airgapped wallet to sign the PSBT.=C2=
=A0</div></div><div style=3D"border-color:rgb(0,0,0)" dir=3D"auto"><br></di=
v><div style=3D"border-color:rgb(0,0,0)" dir=3D"auto">=E2=80=94 Christopher=
 Allen=C2=A0</div></div></div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;paddin=
g-left:1ex;border-left-color:rgb(204,204,204)" dir=3D"auto"></blockquote></=
div></div>

--0000000000007ffa4605cae06f98--