From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1RrowC-0003Ih-7w for bitcoin-development@lists.sourceforge.net; Mon, 30 Jan 2012 10:58:16 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.175 as permitted sender) client-ip=74.125.82.175; envelope-from=andyparkins@gmail.com; helo=mail-we0-f175.google.com; Received: from mail-we0-f175.google.com ([74.125.82.175]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Rrow6-0007Jm-P8 for bitcoin-development@lists.sourceforge.net; Mon, 30 Jan 2012 10:58:16 +0000 Received: by werc1 with SMTP id c1so4113836wer.34 for ; Mon, 30 Jan 2012 02:58:04 -0800 (PST) Received: by 10.216.134.155 with SMTP id s27mr7135218wei.41.1327921084683; Mon, 30 Jan 2012 02:58:04 -0800 (PST) Received: from dvr.localnet (mail.360visiontechnology.com. [92.42.121.178]) by mx.google.com with ESMTPS id l6sm29292258wiv.11.2012.01.30.02.58.02 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 30 Jan 2012 02:58:02 -0800 (PST) From: Andy Parkins To: bitcoin-development@lists.sourceforge.net Date: Mon, 30 Jan 2012 10:57:54 +0000 User-Agent: KMail/1.13.6 (Linux/3.0.0-1-686-pae; KDE/4.6.3; i686; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1845493.WyLT0SFXfN"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201201301058.00650.andyparkins@gmail.com> X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (andyparkins[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1Rrow6-0007Jm-P8 Subject: Re: [Bitcoin-development] BIP-12, 16, 17 X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jan 2012 10:58:16 -0000 --nextPart1845493.WyLT0SFXfN Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable On 2012 January 28 Saturday, Michael Gronager wrote: > If we want more information in a bitcoin address we could just as well > cannibalize it from the checksum - today it is 4 bytes (1 to 4mia) it > could be 2 or 3 bytes (1 to 65k or 16M) and that would not break the > current meaning of the network ID. This would have the same effect - that > you could not mistake two different addresses and create a non-redeemable > transaction. I'm throwing this out as an idea; not necessarily saying it's doable or eve= n=20 good. There is spare capacity in the base58 encoding. - The address hash is 20 bytes - The checksum is 4 bytes - The address type is 1 byte =20 The longest and largest address is therefore 25 bytes of 0xff (it's not=20 possible to all be 0xff of course). Converting those 25 bytes of 0xff to=20 base58... hex: ffffffffffffffffffffffffffffffffffffffffffffffffff base58: 2mXR4oJkmBdJMxhBGQGb96gQ88xUzxLFyG This is 34 base58 symbols. It's not the largest base 58 number that will f= it=20 in 34 symbols though... base58: zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz hex: 20a8469deca6b5a6d367cbc0907d07e6a5584778de27ffffffff vs hex: ffffffffffffffffffffffffffffffffffffffffffffffffff i.e. there are a few unused bits (~5) available in the base58 representatio= n=20 that can be added without changing the number of symbols in the address. Andy =2D-=20 Dr Andy Parkins andyparkins@gmail.com --nextPart1845493.WyLT0SFXfN Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEABECAAYFAk8md7IACgkQwQJ9gE9xL23euACghzfbf/M8MbuM3aHkuaxrXZgv bH0An0nlhsUKB8+K71hHMiH9fwZFu8yR =DhYW -----END PGP SIGNATURE----- --nextPart1845493.WyLT0SFXfN--