From: Nadav Ivgi <nadav@shesek•info>
To: bitcoin-development@lists•sourceforge.net
Subject: [Bitcoin-development] Standard public key base58-check address prefix?
Date: Fri, 21 Jun 2013 23:15:55 +0300 [thread overview]
Message-ID: <CAGXD5f1sOBT7qZdVvyTFLDRu5Bn4BfpWgm=aQi-=M=UMnrSCCg@mail.gmail.com> (raw)
[-- 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 --]
next reply other threads:[~2013-06-21 20:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 20:15 Nadav Ivgi [this message]
2013-06-21 20:25 Nadav Ivgi
2013-06-21 20:41 ` Nadav Ivgi
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='CAGXD5f1sOBT7qZdVvyTFLDRu5Bn4BfpWgm=aQi-=M=UMnrSCCg@mail.gmail.com' \
--to=nadav@shesek$(echo .)info \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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