[bitcoin-dev] Proposal for a few IANA mime-types related to Bitcoin
ChristopherA at lifewithalacrity.com
Tue Aug 31 19:01:23 UTC 2021
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
…and libraries at
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?
— Christopher Allen [via iPhone]
On Tue, Aug 31, 2021 at 11:41 AM Peter D. Gray via bitcoin-dev <
bitcoin-dev at lists.linuxfoundation.org> wrote:
> Hi list!
> I am proposing to register the following MIME (RFC 2046) media types with
> the IANA:
> - aka. a BIP-174 file, in binary
> - does not make any claims about signed/unsigned status; lets leave
> that to the file
> - aka. wire-ready fully-signed transaction in binary
> - aka [BIP-21](
> - 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
> as "encoding=hex" or "encoding=base64" in the optional parameters, just
> "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
> - I have no idea how easily IANA will accept these proposals.
> - current approved mime types:
> @DocHEX || Coinkite || PGP: A3A31BAD 5A2A5B10
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the bitcoin-dev