Professor Hantzen

Member
  • Content count

    167
  • Joined

  • Last visited

  • Days Won

    1

Professor Hantzen last won the day on February 22

Professor Hantzen had the most liked content!

2 Followers

About Professor Hantzen

  • Rank
    Advanced Member

Contact Methods

  • Website URL
    https://twitter.com/phantzen

Profile Information

  • Gender
    Male
  • Country
  1. You can't connect to... what?
  2. You can just do the coinbase thing someone else suggested, but instead of bitstamp go coinbase BTC --> poloniex --> BTC/XRP. As for storage, download one of the ripple wallet programs listed in the "Links & Resources" on this site. The XRP Chat Wallet should be fine. Or you can go for a cold wallet via the appropriate links (but then you can't sell so easily if you need to in a hurry). You can send your purchased XRP to the wallet you set up, either a cold wallet, or in one of the programs - always test with a small amount at every step in this process. Because it's a large amount of money, I would additionally suggest splitting the funds up into packets. Buy and send a few BTC at a time (5-10BTC), and when you trade them for XRP, put that resultant XRP into different wallets that you've set up with the downloaded wallet software. The absolutely most important thing is to store your ripple "secret" securely, this is the string of numbers and letters beginning with "s", looking something like "sUdHekd2d8eeHdnss45kS". The cold wallet or wallet software will show you this and typically warn you to store it safely. This "secret" literally IS your money. No matter what happens to any software you use (say, it stops being supported/developed and a year later when you want to sell it won't run anymore on your latest computer OS), or if you forget the password to your wallet, or whatever else happens, this string of characters is what will give you access to your XRP regardless of the future situation. There will always be another wallet that can import your secret. Or you can do it on an exchange. Essentially, if secrets stop working, *everyone* has lost their XRP. So keeping it safe is as safe as you can get. I can't stress this enough. Many people ignored the warnings in times past and failed to store their secrets instead only storing the password to their wallet - BIG MISTAKE. I would suggest printing out your secrets and keeping them in a few locations. Perhaps also store them on a USB stick with printouts and put it in a bank vault. I recommend the secondary step of not describing what they are accurately. Even disguise them as something else "serial number for Pentium upgrade" or something equally useless-sounding, that maybe you know, and maybe is recorded in your will registered with your lawyer, but no one else knows. Make sure you test all of your secrets to be sure you have them recorded correctly. The easiest way is to paste them each one into top field of the jatchili minimalist ripple client (in the Links section again), then click the "set identity" button and it should come up with the correct ripple address (that you sent your XRP to from polo). This can all be done offline in the case of protecting the sanctity of a cold wallet. (You can download the jatchili client for this purpose - just go to the webpage and Save it from your browser). ABSOLUTELY DON'T STORE YOUR XRP ON AN EXCHANGE. Exchanges can be hacked, go out of business and run off with your money, both things have and may happen to your funds on exchanges. The risk is not worth the convenience of being able to sell in a moments notice. That said, Bitstamp is probably about the most trustworthy in that regard. They've been hacked before (by an employee I believe) and stolen from - and they still protected/covered all their user funds which is about as much as you can ask for.
  3. Oh God I've been in here since 2013. I've ended up somewhat averse to Ripple-authored libraries and roll my own stuff as much as I can. It's too difficult to keep up with their way of tearing everything to pieces over and again. rippled and it's interface is fantastic though. At least its been consistent when it comes to the basics.
  4. Apologies, you need specifically to install version 0.8.0 of ripple-keypairs, so: npm install ripple-keypairs@0.8.0 Should fix the problem. (I've updated github accordingly.) It appears between v0.8.0 and v0.10.0 Ripple has completely broken the API. I probably should know to expect this by now... ;D
  5. 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.)
  6. 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".
  7. @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.
  8. 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*
  9. Correct! But only because all addresses are - in a sense - "wasted" already. (And anything longer than 6 characters may take years to find.)
  10. No. Addresses aren't actually "generated" at all really. All of them already exist. What happens (in principle) is you randomly choose a number between 0 and a really, really, really high number. Odds are that if everyone on earth did this all day for years and years no one would get the same number as anyone else until long after the sun has died That's how bitcoin and ripple protect funds - math and odds. It sounds a little crazy, but it works. (This is a common theme in cryptography...) Ripple addresses aren't "known about" by the network until funds are sent to them, that's the "activating" part (sending 50 XRP for example). At that point, an address is registered on the network and its balance stored forever in the ledger. Prior to that you can "generate" millions of addresses and the network will have no idea, nor any need to know you've done it.
  11. Well, as the name implies, it adds "vanity". On a practical level, when developing, an address containing a familiar string can be easier to spot when trawling through JSON, logs and database tables. Other than that it's probably almost completely pointless. This is correct in principle, but actually the entire address is randomly generated. What the program does is generate hundreds of thousands or millions - ignoring them all - until it finds one that has the string you want in it and prints it to the screen. It can find an address with a three character string in less than 15 seconds if you're lucky, or in up to two minutes if you're unlucky. Four characters may take about 58 times longer, and so on to the power of 58. As such, sufficiently long strings may take longer than the lifespan of our universe to find, unfortunately. I could maybe optimise it a bit, but even if it was written in 100% native assembly, and we commandeered every computer on earth for the effort, we'd likely still have to wait many trillions of years to find something like "rThisIsSuchACoolRippleAddressIsntIt".
  12. Yes, I remember it too! It was funny as I was making this I thought "didn't I code this already?". Maybe I was remembering that other one. I may add case-insensitivity and position. (It'd be easy enough to grep for the latter, just pipe the output to grep '<space>r<search-string' for the beginning, and '<search-string>,' for the end.)
  13. Made this a while ago, just tidied it up and put it online: https://github.com/professorhantzen/ripple-vanity
  14. To rinse and repeat you'd need to send the USDT back to kraken, and convert it to USD again so you can buy BTC. What would keep you from doing that is USDT/USD rate on kraken which is roughly equal to the difference in price in BTC/USD on kraken versus BTC/USDT on poloniex.
  15. I think you need Mac OS X in there?