📅 Original date posted:2021-08-31
📝 Original message: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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20210831/a4aa0e7d/attachment.sig>;
Peter D. Gray [ARCHIVE] /
npub10v…t058y
2023-06-07 22:58:22
in reply to nevent1q…wclq
Author Public Key
npub10vqyu8x3f0lfttk98xc28ppuyufaz4df8x4aspa9w9xz5z05snzq7t058yPublished at
2023-06-07 22:58:22Event JSON
{
"id": "3eb19694fb1538fa14eb8af9dcd45ca0163e344de6c060d55d05c57ef0ee1f02",
"pubkey": "7b004e1cd14bfe95aec539b0a3843c2713d155a939abd807a5714c2a09f484c4",
"created_at": 1686178702,
"kind": 1,
"tags": [
[
"e",
"0102c19bd36d0f378a4cd409e843e7cafde9df6b729698d5a2dd818414f556f0",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2021-08-31\n📝 Original message:Hi list!\n\nI am proposing to register the following MIME (RFC 2046) media types with the IANA:\n\n\nbitcoin/psbt\n\n - aka. a BIP-174 file, in binary\n - does not make any claims about signed/unsigned status; lets leave that to the file\n\nbitcoin/txn\n\n - aka. wire-ready fully-signed transaction in binary\n\nbitcoin/uri\n\n - aka [BIP-21](https://github.com/bitcoin/bips/blob/master/bip-0021.mediawiki)\n - could be just a bare bech32 or base58 payment address\n - but can also encode amount, comments in URL args\n - potentially interesting as a response to 402 - Payment required\n\n\nOther thoughts\n\n- some mime-types are proposed in BIP-71 but those are unrelated to above, and never\n seem to have been registered\n\n- for those who like to encode their binary as base64 or hex, that can be indicated\n as \"encoding=hex\" or \"encoding=base64\" in the optional parameters, just like\n \"text/plain; encoding=utf-8\" does. However, the default must be binary.\n\n- although the above are useful for web servers, they are also useful elsewhere and I\n intend to use them in NFC (NDEF records) where a shorter length is critical.\n\n- I have no idea how easily IANA will accept these proposals.\n\n- current approved mime types: https://www.iana.org/assignments/media-types/media-types.xhtml\n\nThoughts?\n\n---\n@DocHEX || Coinkite || PGP: A3A31BAD 5A2A5B10\n\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 488 bytes\nDesc: not available\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20210831/a4aa0e7d/attachment.sig\u003e",
"sig": "05076dccbe7b752a7a77f85100943eae90ea8495cc80e04200b86ea4cb6e927edf1fde0bc8cff98e0e1bebb2ef718ae6425d080241582ac1f2ff39e210522e17"
}