The "dsv" pattern matching was used when testing/debugging the application, and I forgot to remove it in release build. I've just fixed this in the latest version (1.471).
The download links are in the top post.
Unfortunately I don't have very much time available for further improving this application right now, but I might revisit it in a few weeks.
Topic: 2^256 Deep Space Vagabond - page 8. (Read 38659 times)
Did I win?
can't it just run forever and put the non-zero-balance privkeys into an ascii file?
Is it possibke that the programm always stops when it finds an adress beginning with dsv ??
Would also leave it on when i sleep but after 5-10 mins it stops hilighting an adress with 0 balance but dsv after the first 1.
Can i change this?
Thanks
Would also leave it on when i sleep but after 5-10 mins it stops hilighting an adress with 0 balance but dsv after the first 1.
Can i change this?
Thanks
the more you sleep the higher your chance on luck 
okay, but do i have to click each link to confirm there isnt a match? And it pauses automatically or i do it manually.Sorry for so many questions just i am probally gona leave it on when i sleep and hope i get lucky
cool little program, just one question if we do find an address with bitcoins besides for it beeping will it keep it on the screen or something or how else are we supposed to know that we found some bitcoins?
The program pauses with the current list of 64 addresses generated. On the address where a match was found, the program will show "FUZZY MATCH!" (or similar - don't remember). Double-click the address where "FUZZY MATCH!" is displayed, and the program will retrieve the address's current Bitcoin balance from blockchain.info. It then appears where "If the program finds a match, depending on your screen resolution, you may have to scroll down the list with mouse scroll-wheel to find the address with a match.
cool little program, just one question if we do find an address with bitcoins besides for it beeping will it keep it on the screen or something or how else are we supposed to know that we found some bitcoins?
So, does it do anything cool if you do find a match?
It stops, plays a sound, the text turns light blue, and you can double-click the match to see how much BTC is on the address (checks with blockchain.info). You can then import the public/private key.
So, does it do anything cool if you do find a match?
It stops, plays a sound, the text turns light blue, and you can double-click the match to see how much BTC is on the address (checks with blockchain.info). You can then import the public/private key.So, does it do anything cool if you do find a match?
It stops, plays a sound, the text turns light blue, and you can double-click the match to see how much BTC is on the address (checks with blockchain.info). You can then import the public/private key.
So, does it do anything cool if you do find a match?
just a warning.... don't run random executables linked on this forum... 
Sure, sound advice!
I do guarantee that this app does no malicious things, but I agree that
to be on the safe side in general, either run executables in a secure virtual
machine or sandbox (such as Sandboxie) or compile them from the source.
The (quite short, exactly 75 lines!) source code for this app will be released soon. I need to clean it up a little and make it more readable - it's still a little messy right now.
Very cool Project, even though of course it's a bit 'pointless'. What happens when (as in before the sun dies out) you find a non-zero balance? Also- does it support GPU's? :-)
Also- can you export all these Bitcoin addresses and Private keys? IE: can it double as a key pair generator?
Sure, all addresses along with their private keys are automatically exported to a file on the desktop (the location will be changed to something more sensible in the next release)
i have a multiscreen-environment (4 screens). only blacks out one of them.
where's the key file at?
So where's the serious version?
ETA: More importantly, why isn't this on my phone, yet?
ETA: More importantly, why isn't this on my phone, yet?
Version 1.469 is out, with better support for different screen resolutions and the Hotlist feature bumped to 52 items. (See OP for download)
PS: at 2.5 Taddr/s (about the speed address mining would reach if all Bitcoin's hash power were converted to GPU-optimized address mining code), you have about 0.000000000023% chance of finding one match per 4.54 billion years (age of the earth).
These numbers are for preimages on 160-bit addresses. There's no point in trying to match the (almost) 256-bit private keys anyway.
PS: may I ask how many addresses/s your software can do?
The current version is intentionally VERY slow (only 64 addresses at a time, approximately) - just to show that it's not meant to be taken too seriously. It could easily be made much faster though, as it actually uses lightning-fast Vanitygen address generation routines in the background.
PS: at 2.5 Taddr/s (about the speed address mining would reach if all Bitcoin's hash power were converted to GPU-optimized address mining code), you have about 0.000000000023% chance of finding one match per 4.54 billion years (age of the earth).
These numbers are for preimages on 160-bit addresses. There's no point in trying to match the (almost) 256-bit private keys anyway.
PS: may I ask how many addresses/s your software can do?
((...snip...))
Another fun math thing. Earlier, someone was trying to figure out if 2^256 was closer to the number of atoms in the universe (or the visible universe, or a fraction of these atoms, or the atoms in a person)
2^256 atoms?
Well, every "mol" of hydrogen atoms weighs 1 gram:
(cite) -- Avogadro constant so aprox: 6.02214 * 10^23
great!
Now for some math & logic time:
(6.02214 * 10^23) = number of hydrogen atoms in 1 liter of hydrogen gas at standard temperature / pressure (ideal gas law)
A liter of water weighs approximately 1000 grams (1 kg)
A single water molecule weighs aprox 18 times as much as a single hydrogen atom
Therefore, 55.5 mols of water in a liter (kilogram)
7.806 * 10^26 atoms in 70 kilograms of water. The human body is mostly water.
Assuming we're mostly water, the human body has aprox 2^70 atoms
2^256 hydrogen atoms ... actually I'm just going to stop right now, converting to decimal and bypassing mass calculations:
log(2^256) / log(10) ... you're already much closer to the number of atoms in the visible universe.
... Not to worry though, since there is no point in attempting to exhaust the 256 keyspace:
Only 160 bits worth of hash used to generate bitcoin's 34 "digit" base 58 public key addresses, so you'll VERY likely have many many collisions well before you try a number of keypairs equal to the number of atoms on planet earth.
Another fun math thing. Earlier, someone was trying to figure out if 2^256 was closer to the number of atoms in the universe (or the visible universe, or a fraction of these atoms, or the atoms in a person)
2^256 atoms?
Well, every "mol" of hydrogen atoms weighs 1 gram:
(cite) -- Avogadro constant so aprox: 6.02214 * 10^23
great!
Now for some math & logic time:
(6.02214 * 10^23) = number of hydrogen atoms in 1 liter of hydrogen gas at standard temperature / pressure (ideal gas law)
A liter of water weighs approximately 1000 grams (1 kg)
A single water molecule weighs aprox 18 times as much as a single hydrogen atom
Therefore, 55.5 mols of water in a liter (kilogram)
7.806 * 10^26 atoms in 70 kilograms of water. The human body is mostly water.
Assuming we're mostly water, the human body has aprox 2^70 atoms
2^256 hydrogen atoms ... actually I'm just going to stop right now, converting to decimal and bypassing mass calculations:
log(2^256) / log(10) ... you're already much closer to the number of atoms in the visible universe.
... Not to worry though, since there is no point in attempting to exhaust the 256 keyspace:
Only 160 bits worth of hash used to generate bitcoin's 34 "digit" base 58 public key addresses, so you'll VERY likely have many many collisions well before you try a number of keypairs equal to the number of atoms on planet earth.
... that's what I get for not proofreading sufficiently. NO CLUE where that 2^70 atoms came from. Gonna check my math because I'm suspicious now:
K = 1000 / 18 = 55.55555 (mols of water molecules in 1 kilogram of water)
^ trivial reasoning, so not showing work there.
C = 6.02214 * 10^23 = Atoms in 1 "mol" of anything.
M = K * C = total number of water molecules in a kilogram of water
H = M * 3 * 70 = atoms in a 70 kg human
^water has 3 atoms per molecule, assume 70 KG body mass
(simplified density calculation / calculating with water since humans are mostly water)
ok here we go:
H = M * 3 * 70
(K * C) * 3 * 70
18 * (6.02214 * 10^23) * 3 * 70
10839852000000000000000000 * 3 * 70
H = 2276368920000000000000000000
now to binary:
log(H) / log(2)
62.992379105356328965599428828285 / 0.69314718055994530941723212145818
H = 90.87879...
oops, I'm not sure where I got the earlier value of 2^70
... my bad, but either way, still less than 2^256 atoms in a human
This is why they try to it's common to ask students to show their work / prove everything with math.
Edited:
ACK!!! ok, this time I used the wrong value for K, here's fixed math:
H = M * 3 * 70
(K * C) * 3 * 70
55.555... * (6.02214 * 10^23) * 3 * 70
33456333333333333333333333.333333 * 3 * 70
H = 7025830000000000000000000000
now to binary:
log(H) / log(2)
64.119390868546136633237958001732 / 0.69314718055994530941723212145818
H = 2^92.5 (most people only know their weight to about 3 significant digits anyway)
Version 1.463c is out (see OP), with a fix for a display race condition and a nice ASCII background by hrr
@kuzetsa:
Yeah, I even considered renaming the application to 2^160 DSV at first (but stayed with 256 because even though the valid address space is indeed much smaller, the private key space is still 2^256 if I'm not mistaken - and also, the nerd in me kinda likes the number 256 better )
But thanks for your post, that's the kind of stuff I like to read!
Yeah, I even considered renaming the application to 2^160 DSV at first (but stayed with 256 because even though the valid address space is indeed much smaller, the private key space is still 2^256 if I'm not mistaken - and also, the nerd in me kinda likes the number 256 better
)But thanks for your post, that's the kind of stuff I like to read!
Jump to: