📅 Original date posted:2013-06-21
📝 Original message:Just a small clarification: I was referring to the actual public key,
and not the hash160 of it used for Bitcoin addresses. Its usually not
used, but it is needed for multisig transaction.
On Fri, Jun 21, 2013 at 11:25 PM, Nadav Ivgi <nadav at shesek.info> wrote:
> I'm working on a project that requires users to exchange public keys (for
> multisig transactions).
>
> It seems that hex encoding is usually used to display public keys (i.e. in
> bitaddress and brainwallet), which results in longer strings and lacks the
> 4-bytes verification.
>
> A standard way to encode public keys as base58-check addresses would make it
> easier and safer to display and exchange public keys. All that is really
> needed is deciding on a prefix byte.
>
> Perhaps we can use 0x37/0x38, which results in the letter P (for "Public")?
> It seems like those bytes aren't used for anything yet.
>
> Thanks,
> Nadav
Nadav Ivgi [ARCHIVE] /
npub1f2…ydpll
2023-06-07 15:03:53
in reply to nevent1q…h2d6
Author Public Key
npub1f2w9pm06c4k9ay8rst7757thahg2tfrtd0n645zxrtsqwhvaysrswydpllPublished at
2023-06-07 15:03:53Event JSON
{
"id": "0eae8f58600a40a804c35b6b4d083e8f2f6a6230684de0da468e849e934a9056",
"pubkey": "4a9c50edfac56c5e90e382fdea7977edd0a5a46b6be7aad0461ae0075d9d2407",
"created_at": 1686150233,
"kind": 1,
"tags": [
[
"e",
"2c593270319de24cfc157759bdb647a5548c35a01c5b07132df9e048008250d1",
"",
"root"
],
[
"e",
"409360ad509c5c0ea9a188a5374f2ee4d2d9860078c9a4cd76dc5703c68a26d9",
"",
"reply"
],
[
"p",
"4a9c50edfac56c5e90e382fdea7977edd0a5a46b6be7aad0461ae0075d9d2407"
]
],
"content": "📅 Original date posted:2013-06-21\n📝 Original message:Just a small clarification: I was referring to the actual public key,\nand not the hash160 of it used for Bitcoin addresses. Its usually not\nused, but it is needed for multisig transaction.\n\nOn Fri, Jun 21, 2013 at 11:25 PM, Nadav Ivgi \u003cnadav at shesek.info\u003e wrote:\n\u003e I'm working on a project that requires users to exchange public keys (for\n\u003e multisig transactions).\n\u003e\n\u003e It seems that hex encoding is usually used to display public keys (i.e. in\n\u003e bitaddress and brainwallet), which results in longer strings and lacks the\n\u003e 4-bytes verification.\n\u003e\n\u003e A standard way to encode public keys as base58-check addresses would make it\n\u003e easier and safer to display and exchange public keys. All that is really\n\u003e needed is deciding on a prefix byte.\n\u003e\n\u003e Perhaps we can use 0x37/0x38, which results in the letter P (for \"Public\")?\n\u003e It seems like those bytes aren't used for anything yet.\n\u003e\n\u003e Thanks,\n\u003e Nadav",
"sig": "aa3aecf9c23cfefaef0c3ba6911ec5f7dd5c920e0638618d38f7a832e31412e7a2b398636f769ae4f3507bd75d33ce238c317db97431c3bc25fab867a1ac0a66"
}