path: root/29/ce0a8d769aad33e26a46869940896eae813e0c

Return-Path: <christophera@gmail.com>
Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 4729FC000E
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 31 Aug 2021 20:03:00 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp1.osuosl.org (Postfix) with ESMTP id 327B58258D
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 31 Aug 2021 20:03:00 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.402
X-Spam-Level: 
X-Spam-Status: No, score=-1.402 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001,
 HEADER_FROM_DIFFERENT_DOMAINS=0.248, HTML_MESSAGE=0.001,
 RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001]
 autolearn=no autolearn_force=no
Authentication-Results: smtp1.osuosl.org (amavisd-new);
 dkim=pass (2048-bit key)
 header.d=lifewithalacrity-com.20150623.gappssmtp.com
Received: from smtp1.osuosl.org ([127.0.0.1])
 by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id y5Q79dFdtRR1
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 31 Aug 2021 20:02:57 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
Received: from mail-ua1-x92f.google.com (mail-ua1-x92f.google.com
 [IPv6:2607:f8b0:4864:20::92f])
 by smtp1.osuosl.org (Postfix) with ESMTPS id 2185C80A7B
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 31 Aug 2021 20:02:57 +0000 (UTC)
Received: by mail-ua1-x92f.google.com with SMTP id m39so78025uad.9
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 31 Aug 2021 13:02:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=lifewithalacrity-com.20150623.gappssmtp.com; s=20150623;
 h=mime-version:references:in-reply-to:from:date:message-id:subject:to
 :cc; bh=rZ25zfXXg2eOlq2iZIVLu2iqy6xI7pajNjZWcWru2ZY=;
 b=PLyugPtj1JMCUyoFbatzSCOYeXiIswLShZ+AE4oe7libvjgLPx1kZ0133t817b68Kg
 wVSZ5uvV0w+7IjlpKo7C9ta9dyeNGq8l225NSVqGGup8viR6G8/oFoOIWijayJ3nvAPL
 TJmVFoA9iG9GZrBlyF2AFznNpJzAznRw+v8sb9/bizaeOqnABREtvep727XQCHMIIWJW
 VWtdm4DIOMfoqRXITx+Xs+snL9M7hpBOyU60CiYkLVYge3z3drM7RkOGVG2FMaYoxFkO
 2mAcRdl++g5QrSJU4g75+K8HmV68P3DQHwsIMOXlR+m14sC7uVbQmsn6nMhVnnXXmd1h
 BdIQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to:cc;
 bh=rZ25zfXXg2eOlq2iZIVLu2iqy6xI7pajNjZWcWru2ZY=;
 b=QouR8g/xs68U8iA/VvQT3ngybZuuEDaOegGNQfrt3zxbFqAYd9Y/2ozX4JAoEqLQz4
 dNtP59E0IIS1lHmHn028gesek11xuVELqhUwq2VWc+g1famMrzuhPntNZ29wqvlZVxtn
 GfPNNb9cH3nnsF8CzQMam3tzYve5SfYX70iLgWoMTgqVou1HW046/ci/89wvqay2rNhB
 sNOSjZR7R25C/+ZRMeH3v+PjZQRTHQp4MQmbPuD3PCbd3ghianAEuIa27mFhqEx/mlzz
 e/8pHk2Q95FABHRy6+03SM38i+LKZwTPdm713AVdD13LbtB2PuJkQI3O6rSJRf/wwfaI
 NHew==
X-Gm-Message-State: AOAM532Q5AjDU/3U7kwOXnKvCjamko7Y+Ftan0JBxR67dAaaTL7ytxKb
 jEFz9PHP0FHeeZEf9oCNAQSC2bf1VxkNlrdzJZs=
X-Google-Smtp-Source: ABdhPJxxDLX9DztsK40hqxH0vWSHswz6Cva/15a2fXWt+JeHVm9cswU7YChaYUK4wOfBRIQwEkFfayx6WOs8pM1pUj4=
X-Received: by 2002:ab0:496b:: with SMTP id a40mr20835375uad.33.1630440175693; 
 Tue, 31 Aug 2021 13:02:55 -0700 (PDT)
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"
X-Mailman-Approved-At: Tue, 31 Aug 2021 22:12:22 +0000
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
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Aug 2021 20:03:00 -0000

--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--