Our operations hinge in no way on one payment processor. EasyCoin hopes to provide the widest choice of top-up methods and selection of crypto currencies.

EasyCoin is still undergoing the BETA phase of testing in some jurisdictions as we continue to add payment options for varying jurisdictions.

EasyCoin will have a delayed roll out in the US, this is due to awaiting the written clarification from FinCEN with regards to the basis of license requirements for our specific operation. This is unfortunate in the short term, however having these clarifications in writing will benefit the long term operations.

Availability in the UK will be online once the payment service provider goes online there, the same applies for Norway, Denmark, Sweden and Russia. We are working closely with other payment service providers to enable the platform to become available in other jurisdictions throughout Europe and the Rest of the World.

We offer apologies to those BETA testers and the wider public who are awaiting the commencement of operations in the US.

Thanks for the response -- can pointbiz confirm this?

Thanks for your responses and all your work on bitaddress.org.

I'm getting ready to generate a batch of public-private key pairs for long term cold storage. If I boot my system to an Ubuntu LiveCD, can I just use the bitaddress.org .html file by itself, or do I need to include the other java-related files to generate functional, secure key pairs?

Why would it be? Entropy is not 'used up'. Recreating the object won't save you if you don't have enough entropy.


In fact in bitaddress.org a small amount entropy is constantly added with every mouse move, mouse click and key press.


edit3: On further inspection I've found this is not true. Even though seedTime() is invoked, the entropy is not added to the PRNG used to create private keys. There is a TODO in the source about reseeding so the author has this in mind.




It's pretty clear to me that the code is like this to extract two bytes from each call of Math.random()

So the first line in that loop creates a random number in the range [0, 65536) which is the standard 16 bit range.
The next line with the right shift by 8 adds the upper 8 bits to the sr.pool array, the line after that adds the lower 8 bits to the sr.pool array.

I'm not too sure why the author doesn't extract one byte at a time. Although I'm pretty confident it won't steal your bitcoins doing it either way.


Soon enough, all these fears can be rested when something like this is added. I imagine a nice text entry box where the user can type in anything they like. I'll be extracting randomness from /dev/random on my LiveCD and copypasting the result into the text entry box.
Other paranoid people might be taking a photo with their hand covering the camera, since the fluctuations on the CCDs are a good source of randomness. Others might even download from random.org

edit: needless to say you could do that now by modifying the source. Add this to the code right after sr.seedInt(window.screenY); when sr is initialised.

Then put whatever you want into secret_seed and that entropy will be added to the RNG.
I'm not responsible for any loss of bitcoins. Peer review of my code happily accepted.

edit2: for completeness I'd run this on the terminal to obtain 16 bytes (128 bits) of entropy.

I don't understand the code well enough to answer your specific concern.

My biggest concern at bitaddress.org is the use of external javascript files. This gives the host of those files the possibility to execute any javascript on the page. They could easily insert a function that sends the private keys to a third party website. If that's done only 1 of 10 times, it's hard to get caught.

Also, a week ago when I was trying to teach my college how to create a wallet, bitaddress.org displayed invalid security certificate -errors. Needles to say we stopped using the site immediately. Was a pretty embarrassing situation for me.

I'm taking a look at cascasius's address utility that included Bip0038 two factor encryption. This post on reddit made me curious:
http://www.reddit.com/r/Bitcoin/comments/1q7inm/this_paper_wallet_now_contains_0225_btc_and_is/

 

Thanks
If you have any comments/suggestions/critics I'd be happy  

Honestly, If you have to post questions all across the internet to learn how to secure your system, then a BitCoin gambling site may not be for you.

If I was programming a bitcoin gambling site I wouldn't share any of my sites inner workings anywhere online.


I would suggest asking specific questions such as, What is the benefits of writing to my database using PDO vs mysqli or mysql?

The other thing you could do is hire a professional to come in and secure your system for you.

Good luck.

Well that's simple enough, just take the low-order bits. For your application you may or may not require a salt.

The idea works; whether it is a good idea or not depends on your application.

You might want to take the hash of the block and concatenate it with some arbitrary string, then hash it once more to get more randomness. A block hash alone has a bias towards lower numbers.