* [Bitcoin-development] Standard public key base58-check address prefix?
@ 2013-06-21 20:25 Nadav Ivgi
2013-06-21 20:41 ` Nadav Ivgi
0 siblings, 1 reply; 3+ messages in thread
From: Nadav Ivgi @ 2013-06-21 20:25 UTC (permalink / raw)
To: bitcoin-development
[-- Attachment #1: Type: text/plain, Size: 607 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1466 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Bitcoin-development] Standard public key base58-check address prefix?
2013-06-21 20:25 [Bitcoin-development] Standard public key base58-check address prefix? Nadav Ivgi
@ 2013-06-21 20:41 ` Nadav Ivgi
0 siblings, 0 replies; 3+ messages in thread
From: Nadav Ivgi @ 2013-06-21 20:41 UTC (permalink / raw)
To: bitcoin-development
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@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
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bitcoin-development] Standard public key base58-check address prefix?
@ 2013-06-21 20:15 Nadav Ivgi
0 siblings, 0 replies; 3+ messages in thread
From: Nadav Ivgi @ 2013-06-21 20:15 UTC (permalink / raw)
To: bitcoin-development
[-- Attachment #1: Type: text/plain, Size: 607 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 836 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2013-06-21 20:41 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-06-21 20:25 [Bitcoin-development] Standard public key base58-check address prefix? Nadav Ivgi
2013-06-21 20:41 ` Nadav Ivgi
-- strict thread matches above, loose matches on Subject: below --
2013-06-21 20:15 Nadav Ivgi
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox