From: "Peter D. Gray" <peter@coinkite•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] Proposal for a few IANA mime-types related to Bitcoin
Date: Tue, 31 Aug 2021 14:27:41 -0400 [thread overview]
Message-ID: <20210831182741.GV91472@coinkite.com> (raw)
In-Reply-To: <mailman.9346.1630015566.1160.bitcoin-dev@lists.linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 1352 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next parent reply other threads:[~2021-08-31 18:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.9346.1630015566.1160.bitcoin-dev@lists.linuxfoundation.org>
2021-08-31 18:27 ` Peter D. Gray [this message]
2021-08-31 19:01 ` Christopher Allen
2021-08-31 19:18 ` Peter D. Gray
2021-08-31 20:02 ` Christopher Allen
2021-08-31 19:46 ` Andrew Chow
2021-09-01 13:39 ` Peter D. Gray
2021-09-02 10:52 ` Dr Maxim Orlovsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210831182741.GV91472@coinkite.com \
--to=peter@coinkite$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox