From: "Luke-Jr" <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net,
Amir Taaki <zgenjix@yahoo•com>
Subject: Re: [Bitcoin-development] Quote on BIP 16
Date: Sun, 29 Jan 2012 00:15:58 -0500 [thread overview]
Message-ID: <201201290015.59665.luke@dashjr.org> (raw)
In-Reply-To: <1327813841.99379.YahooMailNeo@web121006.mail.ne1.yahoo.com>
On Sunday, January 29, 2012 12:10:41 AM Amir Taaki wrote:
> 2 compressed pubkeys
2 compressed pubkeys are 33 bytes each. Add 1 bytes for the N (n-of-m), 1 byte
for the address version, and finally the 4 byte checksum, you get a total of
72 bytes. But these are *bytes* - to get an address, you also need to base58
encode it: this yields a 99 character address.
next prev parent reply other threads:[~2012-01-29 5:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-29 4:52 Amir Taaki
2012-01-29 5:10 ` Amir Taaki
2012-01-29 5:15 ` Luke-Jr [this message]
2012-01-29 5:23 ` Alan Reiner
2012-01-29 8:14 ` Gregory Maxwell
2012-01-29 5:19 ` Gregory Maxwell
[not found] ` <1327835941.47827.YahooMailNeo@web121006.mail.ne1.yahoo.com>
2012-01-29 11:19 ` [Bitcoin-development] Fw: " Amir Taaki
2012-01-29 14:30 ` Gavin Andresen
2012-01-29 14:40 ` Luke-Jr
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=201201290015.59665.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=zgenjix@yahoo$(echo .)com \
/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