Addresses - Shortening and Changing first character

[The Goat Master]

Using the bitcoin code, is it possible to change the starting character as well as the length of the address?

(e.g. instead bitcoin addresses start with B and are always 15 characters long)

What are the starting character base 58 codes?  (The ones used in base58.h to mark new addresses, example: F is 35)

[1713864149]

1713864149

[1713864149]

1713864149

[1713864149]

1713864149

[danneu]

I'm not sure I understand.

Here's what an address is off the top of my head:

Code:

(base58/encode (concat version-byte,
                       (rmd160 (sha256 public-key)),
                       (take 4 (sha256 (sha256 (concat version-byte
                                                       (rmd160 (sha256 public-key))))))

You can't change any of that without garbling data.

[kjj]

The short answer is no.

The address encoding scheme includes a version byte which forces the first byte to take on a specific value (or one of two values, depending on the byte).  For it to be a bitcoin address, it must be 0 or 5, giving a leading character of 1 or 3.

See here, but note that the list is both incomplete (in the sense that there are many other address systems not listed, and new ones showing up every day), and far too long (in the sense that only a couple of them are actually valid for bitcoin).

As to the length, there isn't much to be done there.  The length is fixed by the size of the hash and the encoding system.  Some hashes lead to (very slightly) shorter addresses.  Key compression does not help here (because the hash of the compressed key is used, and that hash is the same size as the hash of the uncompressed key).

There are other schemes that are capable of generating short-ish addresses.  See Casascius's mini format, for an eample.

[algorista]

At some point a system similar to DNS should arise, to improve the situation of addresses being not memorizable.

[gmaxwell]

At some point a system similar to DNS should arise, to improve the situation of addresses being not memorizable.

You should not be reusing addresses. If you want memoriable addresses, use a https URL that issues a bitcoin payment URL in response to loading it.

[r3wt]

At some point a system similar to DNS should arise, to improve the situation of addresses being not memorizable.

You should not be reusing addresses. If you want memoriable addresses, use a https URL that issues a bitcoin payment URL in response to loading it.

you're an effing genius dude. one problem with in face transactions would be getting your address from your mobile device to the machine at the checkout. qr codes cover this issue.

the remaining issue is online payments. your url idea could be a great start.

+1

[algorista]

At some point a system similar to DNS should arise, to improve the situation of addresses being not memorizable.

You should not be reusing addresses. If you want memoriable addresses, use a https URL that issues a bitcoin payment URL in response to loading it.

That's a good idea! Simple and effective.

[The Goat Master]

At some point a system similar to DNS should arise, to improve the situation of addresses being not memorizable.

You should not be reusing addresses. If you want memoriable addresses, use a https URL that issues a bitcoin payment URL in response to loading it.

That's a good idea! Simple and effective.

e.g. If you go to mybitcoinaddy.com, it would load bitcoin:123243124321 and make a tx to send to that addy?
(I forget the exact link)

[inform]

Yeah nice idea 

[e4xit]

Careful with this, but you could have a look at this site for ideas:

https://btc.to/