From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138]) by lists.linuxfoundation.org (Postfix) with ESMTP id 78D92C000E for ; Tue, 31 Aug 2021 19:26:49 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id 57EC3823CB for ; Tue, 31 Aug 2021 19:26:49 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no 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 kNThdNNQJVlB for ; Tue, 31 Aug 2021 19:26:45 +0000 (UTC) X-Greylist: delayed 00:08:41 by SQLgrey-1.8.0 Received: from smtp99.iad3b.emailsrvr.com (smtp99.iad3b.emailsrvr.com [146.20.161.99]) by smtp1.osuosl.org (Postfix) with ESMTPS id 04C9E8101B for ; Tue, 31 Aug 2021 19:26:44 +0000 (UTC) X-Auth-ID: peter@coinkite.com Received: by smtp5.relay.iad3b.emailsrvr.com (Authenticated sender: peter-AT-coinkite.com) with ESMTPSA id 74FB54011E; Tue, 31 Aug 2021 15:18:02 -0400 (EDT) Date: Tue, 31 Aug 2021 15:18:00 -0400 From: "Peter D. Gray" To: Christopher Allen Message-ID: <20210831191800.GW91472@coinkite.com> Reply-To: Peter Gray References: <20210831182741.GV91472@coinkite.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Organization: Coinkite Inc. (www.coinkite.com) X-Classification-ID: 7ae598fa-276c-4d41-869c-3aeafc414ce6-1-1 X-Mailman-Approved-At: Tue, 31 Aug 2021 22:12:22 +0000 Cc: Bitcoin Protocol Discussion , Wolf McNally , Shannon Appelcline 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Aug 2021 19:26:49 -0000 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@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@lists.linuxfoundation.org > > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > >