Ripple vanity address generator

[Guest plutopark]

Ok, a lot of that I got, some of the cyrptography I already knew, and some I didn't understand, at all. Is the set of all addresses the set of all possible addresses, or is the set limited, somehow, to those that are, for instance the product of a prime number and the square root of the next greatest number that has a square root?

Also, as enrieque posits, what happens IF two same addresses DO get created?

Edited April 26, 2017 by plutopark

[enrique11]

20 minutes ago, Professor Hantzen said:

Correct!  But only because all addresses are - in a sense - "wasted" already.   (And anything longer than 6 characters may take years to find.)

Crazy mind-boggling stuff, considering how fast computers are.

[Professor Hantzen]

42 minutes ago, enrique11 said:

One thing I was always curious about: on the extremely unlikely chance that two wallets generated have the same public address, does the addressing scheme allow for such an occurence, or is there a built-in fail-safe against such an unlikely occurence, and if no fail-safe how do non-unique public addys get resolved in such an instance?

There is no failsafe that I'm aware of.  Well, other than the failsafe that the entire universe spontaneously turning into a gigantic pink duck is probably more likely.

*quack*

[Professor Hantzen]

@enrique11 & @plutopark This may freak you out a little.  It's a "database" of all private and public keys for every bitcoin wallet (and it's real).  You can click all you want and you'll never find a wallet with anything in it (excepting a couple at the edges that have since been emptied, because people either made mistakes coding, or intentionally hid coins there for others to find).  The same thing could be created for Ripple, or just about any cryptocurrency.  It doesn't mean anything bad, it's just a somewhat disconcerting way of looking at the math.  

More info here.

[enrique11]

10 minutes ago, Professor Hantzen said:

@enrique11 & @plutopark This may freak you out a little.  It's a "database" of all private and public keys for every bitcoin wallet (and it's real).  You can click all you want and you'll never find a wallet with anything in it (excepting a couple at the edges that have since been emptied, because people either made mistakes coding, or intentionally hid coins there for others to find).  The same thing could be created for Ripple, or just about any cryptocurrency.  It doesn't mean anything bad, it's just a somewhat disconcerting way of looking at the math.  

More info here.

 

Right, it's intuitive, if you go look inside any randomly generated wallet you'll find that 99.9999999999999999999999999...9%  where you have a string of nines of over length fifty (? more guess work here) something of them are currently empty, if you could live long enough to look through them. Your eyes would dry out and fall out of their sockets ;P

 

Edited April 26, 2017 by enrique11

[Eik]

When XRPTalk was still active, I wrote a post on how to 'hack' any ripple address by trying to get the secret key of high volume wallets (e.g. Ripple's XX billion wallets) via exactly this way.

I concluded you better waste your time and energy on mining bitcoin... that is like infinitely more profitable

That database is cool though. You can just make one for Ripple and browse through it until you find the billion XRP wallets

[Eik]

6 hours ago, Professor Hantzen said:

@enrique11 & @plutopark This may freak you out a little.  It's a "database" of all private and public keys for every bitcoin wallet (and it's real).  You can click all you want and you'll never find a wallet with anything in it (excepting a couple at the edges that have since been emptied, because people either made mistakes coding, or intentionally hid coins there for others to find).  The same thing could be created for Ripple, or just about any cryptocurrency.  It doesn't mean anything bad, it's just a somewhat disconcerting way of looking at the math.  

More info here.

Lol at his FAQ:

Quote

[...]
Q: Can I search by private key?
A: Yes. @see API documentation.

Q: Should I search by private key?
A: No. I log and steal everything.
[...]

I wouldn't be surprised if he makes more money from stupid people giving him their secret keys than from the donations.

Quote

[...]
Q: Are donations really welcome?
A: No.

 

[pucksterpete]

Very cool,

Me not so technical, how would I go about using this js script and generate some vanity address's.

Did a little search last night and downloaded node v6.1, opened a cmnd prompt and went to the dir where the ripple-vanity.js was and typed in node ripple-vanity.js.    After that, i'm lost

someone help me find my way please 

[Professor Hantzen]

2 hours ago, pucksterpete said:

Did a little search last night and downloaded node v6.1, opened a cmnd prompt and went to the dir where the ripple-vanity.js was and typed in node ripple-vanity.js.    After that, i'm lost

someone help me find my way please 

Did it come up with the usage instructions after you typed node ripple-vanity.js?  If it didn't and instead came up with an error, at a guess you probably haven't also installed the dependency "ripple-keypairs".  To do that, you'll need to type "npm install ripple-keypairs" (best from inside the ripple-vanity.js directory).

However, to do *that* you might also need to install "npm" if it wasn't included in node v6.1.  node and npm kind of go together. npm is the "node package manager", it installs the different building blocks that scripts and modules may need to do what they do.  The vanity script only needs one building block, which is made by Ripple themselves, called "ripple-keypairs".

Edited April 26, 2017 by Professor Hantzen

[pucksterpete]

cool, I noticed that I have a folder called ripple-keypairs

got the usage instructions

Is this just a finder or does it allow u to create vanity ripple address's?

 

Edited April 26, 2017 by pucksterpete

[Professor Hantzen]

55 minutes ago, pucksterpete said:

cool, I noticed that I have a folder called ripple-keypairs

got the usage instructions

Is this just a finder or does it allow u to create vanity ripple address's?

That's great! Then all you need to do is type:

node ripple-vanity.js pete 500000

It should say:

Searching 500000 addresses for "pete"...
0%

And the 0% will increase every so often as it advances through the search.  For a four-character search string that may take about half an hour to reach 100% (depending on the speed of your computer), and might turn up 2-3 new addresses you can use that contain the string "pete" somewhere.

An address finder and creator is (or should be) the same thing.  If you don't want to wait to see it work, Ctrl-C (quit) the above command, and try something like:

node ripple-vanity.js xrp 10000

This will be much faster, probably in about a minute you'll have 2-3 addresses come up.  They will be in the form:

<number of tries to find>, <public ripple address>, <private ripple secret>

If you paste any output here, make sure to erase/censor the "secret" part if you ever intend to use that address! (The secret is what you can use in any of the downloadable ripple wallets, or on gatehub for example.)

[pucksterpete]

hmmm getting an error

Quote

C:\Users\pete\nodes\noding>node ripple-vanity.js xrp 10000
Searching 10000 addresses for "xrp"...
0%C:\Users\pete\nodes\noding\ripple-vanity.js:39
                temp_wallet = kp.generateWallet();
                                 ^

TypeError: kp.generateWallet is not a function
    at Object.<anonymous> (C:\Users\pete\nodes\noding\ripple-vanity.js:39:20)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.runMain (module.js:604:10)
    at run (bootstrap_node.js:393:7)
    at startup (bootstrap_node.js:150:9)
    at bootstrap_node.js:508:3

 

[tulo]

1 hour ago, pucksterpete said:

hmmm getting an error

 

Probably you installed ripple-keypairs in the wrong place. But that is strange because it should trow an error before.

BTW for next commit @Professor Hantzen, you should include a package.json in which you put the dependancy to ripple-keypairs, so that doing npm install inside your repo, it will automatically install the dependancy.

[Duke67]

There is no function like "generateWallet" in ripple-keypairs, only "generateSeed". I think that @Professor Hantzen forgot to include some additional dependency.

 

 

[Duke67]

@tulo, just run "npm init" before "npm install..." and that will generate the JSON for you.