shorter bitmessage addresses

[chan] bitmessage
Aug 13 02:38

Is it possible to make a bitmessage address three bytes shorter instead of two shorter? Would a 3-byte shorter address even work? If so how do I do this?

[chan] bitmessage
Aug 13 03:08

Yes. Yes. Put this in keys.dat: [bitmessagesettings] numberofnullbytesonaddress = 3 Then run BM, generate address.

BM-87VXuGeasCe92n5vNQKtXjGDJg9x4wZ91GV
Aug 13 03:36

Yes. Yes. Put this in keys.dat: [bitmessagesettings] numberofnullbytesonaddress = 3 Then run BM, generate address.

BM-87VXuGeasCe92n5vNQKtXjGDJg9x4wZ91GV
Aug 13 03:40

> Would a 3-byte shorter address even work? Depends on implementation. Beamstat indicates this message is from BM-87VXuGeasCe92n5vNQKtXjGDJg9x4wZ91GV but it is actually from BM-5oRECUteKSTK94VoEfazE1SukkcjQPa

[chan] bitmessage
Aug 13 03:45

I already tried that, ran it for hours, and it would not work. It should only take 3 to 5 hours at most. Suggestions?

[chan] bitmessage
Aug 13 03:46

how was BM-5oRECUteKSTK94VoEfazE1SukkcjQPa generated?

[chan] bitmessage
Aug 13 05:36

Just keep it running until it finds one. It takes as long as it takes - could be seconds, could be days.

[chan] bitmessage
Aug 13 05:58

Can anyone confirm that it actually works? I don't feel like leaving it on for days to find out it does not work. Who has actually done it, and got a resulting, shorter address that functions?

BM-87ZQse4Ta4MLM9EKmfVUFA4jJUms1Fwnxws
Aug 13 15:54

PyBitmessage also displays this message as sent from BM-87VXuGeasCe92n5vNQKtXjGDJg9x4wZ91GV.

[chan] bitmessage
Aug 13 16:38

I ran it for 12 hours with setting to 3 bytes. It did not generate any address.

BM-5oNWNASpdYV5o3MSpv5w2XAYKPA7wzJ
Aug 14 03:31

> It did not generate any address But it didn't fail did it? You gave up. You giving up is not a bug. If my maths is right, the odds of finding a 3 null byte address is 1 in 16,777,216. If it takes you 3 minutes on average to generate a 2 null byte address then it should take you 12 hours and 48 minutes on average to generate a 3 null byte address. Remember though we are talking about averages - if you find one in 1 hour and another after 24 hours and 36 minutes, your average is 12 hours and 48 minutes.

[chan] bitmessage
Aug 14 03:57

Actually he is right to be concerned. There has long been the possibility that BM can get stuck in an infinite loop in pointMult if an error occurs. Although this should be evident in the terminal as BM will flood the terminal with the error.

[chan] bitmessage
Aug 14 04:54

I used the chanerator with a loop to crank out a few megabytes of keys. I grepped the results. So far I got 3 addresses that have 3 null bytes. It took about 18 hours. If your are running an i7 or xeon chip with 8 cores you should be able to get at least ten times as many, or perhaps 30+ in 18 hours. If you iterate the script using 8 instances of bash your linux should automatically distribute the bash threads to different cores.

[chan] bitmessage
Aug 14 04:56

The chanerator script generates them much, much faster than the bm interface.

[chan] bitmessage
BM-2cWy7cvHoq3f1rYMerRJp8PT653jjSuEdY

Subject Last Count
Dandelion Aug 21 09:31 2
how to export keys from Bitmessage Aug 21 06:47 7
Bitmessage Rocks Aug 20 17:37 1
block a BM address from a chan Aug 20 11:03 3
Is anyone even online at this moment? Aug 20 08:43 4
All green peers 127.0.0.1? Aug 19 09:07 5
Chips without backdoors Aug 18 19:10 4
New warnings in log Aug 17 21:00 20
Yellow peers and green peers Aug 16 20:59 4
cannot import name bmpow Aug 15 12:36 2
Brute forcing BM addr's Aug 15 07:58 2
Bitmessage crashes when posting Aug 14 05:51 10
plz assist. are you a netcat or SSH tunnel guru? Aug 14 05:01 4
shorter bitmessage addresses Aug 14 04:56 14
Why Python? Aug 13 10:45 16
Nerd Bully Aug 13 05:17 1
Bitmessage not connecting Aug 12 04:16 64
Feature idea Aug 10 03:30 10
Local nodes won't connect properly Aug 9 15:51 28
I do any thing in iran for BTC Aug 7 15:36 3
Bitmessage feature request Aug 7 12:50 4
query about short addresses Aug 7 06:54 4
Curious Aug 5 22:39 8
Full time nodes Aug 5 13:50 9
changes to the dodobit server Aug 5 11:05 2
Received Date Aug 5 06:04 13
apinotifypath Aug 4 06:04 9
BM <-> TOR Aug 3 13:19 12
BM Bandwidth Aug 2 14:11 11
When I try to register BM, collided with your key Aug 2 13:51 12
Received Date Aug 1 21:34 4
Bitmessage reminds me of ... Aug 1 14:36 3
I need help Aug 1 13:08 3
Response from Bitmessage Dodo Server Aug 1 02:25 1
Streams and bloom filter Jul 31 21:25 3
Questions about bitmessage streams Jul 31 21:25 1
TTL question Jul 31 08:03 3
API JSON index error Jul 31 07:22 3
API question Jul 30 11:22 7
MiNode Jul 30 07:19 3
Yes it's obvious my BM private keys have been stolen.... Jul 29 19:50 2
Keys.dat options Jul 29 04:56 3
Bitmessage and I2P no longer working Jul 28 22:39 10
Connect Bitmessage only to .onion nodes Jul 27 13:22 3