Re: [bitcoin-dev] Proposal for a few IANA mime-types related to Bitcoin

From: Christopher Allen <ChristopherA@lifewithalacrity•com>
To: Bitcoin Protocol Discussion
	<bitcoin-dev@lists•linuxfoundation.org>,
	Peter Gray <peter@coinkite•com>,
	 Shannon Appelcline <shannon.appelcline@gmail•com>,
	Wolf McNally <wolf@wolfmcnally•com>
Subject: Re: [bitcoin-dev] Proposal for a few IANA mime-types related to Bitcoin
Date: Tue, 31 Aug 2021 12:01:23 -0700	[thread overview]
Message-ID: <CACrqygDZGWxrv+3w=gmwVRO4iTLYJnn8QLBEwNQ_EdkXNr46Ww@mail.gmail.com> (raw)
In-Reply-To: <20210831182741.GV91472@coinkite.com>

[-- Attachment #1: Type: text/plain, Size: 2447 bytes --]

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
>

[-- Attachment #2: Type: text/html, Size: 3869 bytes --]