Hacker Newsnew | past | comments | ask | show | jobs | submit | icedicedavid's commentslogin

Yes, there are many ways to buy sell bitcoins. One of YC's company Coinbase is a good place to start: http://coinbase.com

Then there are many more such as http://bitstamp.net

http://mtgox.com used to be the biggest, but now they are slow to withdraw in USD.

You can see the pricing of bitcoin across multiple exchanges here: http://bitcoincharts.com/markets/


Back in July, TradeFortress, the operator of input.io claimed that 0 coins are store on the web facing server.

https://bitcointalk.org/index.php?topic=251553.0


I guess this one was removed too


Our casino is provably fair, which means all bets can be verified cryptographically to verify that we do not take advantage of our users. The house edge is clearly designed to be 2%, which means we return 98% of all the wager back to the players. Players clearly can choose their chance of winning with corresponding payout. Everything we do is transparent, including our profit, how much is in the bankroll. Our rule is our promo is for new users only, and this user created like 20 accounts in the last 3 hours trying. He is clearly not playing by the rules, how are we wrong for blocking his fraudulent behaviour?

all these account he made claimed our credit over and over again just earlier today:

@h7fVandermeulen

@Sfi_Stawski1010

@BQk_Mikadze4232

@8Rl_Moljevic505

@sotnd1996

@_VupEquis8648BY

@i9xHazlip4159EU

@gXtKudla4403HHC

@_uTjJugovic7828

@_wljPines1662BT

@DTt_Przybyszews

@_hogElyan9488GW

@_vdaTournaments

@_mijLyche6529MF

@_UqtNewlands354

@5ox_Ferencik217


To those unfamiliar, it's probably fair but only up to the point where you expect the site to be serving up the same code every time. It's a bit like JavaScript crypto; makes you feel good but has little bearing on anything in the real world.

The server sends the client a hash of a secret, the client sends a locally generated nonce back, and the server hashes the two and determines the outcome. The idea being that the server can't change the result because the secret has already been verified as the same as before they rolled by the client via the previously exposed hash. Still relies on the code being served to not be changed on every load, which is a false assumption to make.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: