... Last day today with reduced house edge... I am having the honour to announce 1 year of bitbattle.me!bitbattle.me is now one of the longest running dice sites, with a 100% clean history - no thefts, no scams, no complaints! This clearly deserves a celebration! Therefor I am happy to present the Anniversary Deal: 1% house edge discount!
House edge is reduced by 1% to an all-time low of 0.9%
This anniversary deal will end on 2013-11-7.
May the luck be with you  |
|
|
|
Ok everybody keeps mentioning the problem of hackers, so what about games where its more difficult to hack, e.g. racing games. Would anyone be interested in winning BTC for winning a race of Extreme Tux Racer?  Why do you think a racing game is harder to hack than an FPS? |
|
|
|
I am having the honour to announce 1 year of bitbattle.me!bitbattle.me is now one of the longest running dice sites, with a 100% clean history - no thefts, no scams, no complaints! This clearly deserves a celebration! Therefor I am happy to present the Anniversary Deal: 1% house edge discount!
House edge is reduced by 1% to an all-time low of 0.9%
This anniversary deal will end on 2013-11-7.
May the luck be with you ... 2 days remaining with reduced house edge! |
|
|
|
|
...3 days remaining with reduced house edge...
|
|
|
|
|
...4 days remaining with reduced house edge...
|
|
|
|
|
...7 days remaining with reduced house edge...
|
|
|
|
Two updates on the documentation: - As some user pointed out, the parameters in the callback are NOT in alphabetical order. (http://www.bitcoinmonitor.net/help/)
- Your agent ID is now displayed in the dashboard after the agent's name. Also the API docs have been update with the info where to get the agent ID
And someone added bitcoinmonitor.net to ProgrammableWeb: http://www.programmableweb.com/api/bitcoinmonitor - Thank you  |
|
|
|
|
...8 days remaining with reduced house edge...
|
|
|
|
|
...9 days remaining with reduced house edge...
|
|
|
|
I am not very clear about incoming and outgoing transactions fees , please help!
Actually it is quite simple: Incoming transactions are checked to prevent trivial double-spend attempts: If a transaction consists of unconfirmed inputs it needs to have a transaction fee of at least 0.0001 BTC. Usually you don't really have to care about this, this is all done automatically by your wallet software. The transaction fee for payouts is calculated the same way the official bitcoin-qt client does. The txfee depends on the size of the transaction. While a session is running the payout is calculated including the estimated transaction fee. Sometimes this estimation is not exactly matching the real tx fee, because you only know the exact fee when the transaction gets created. But usually the estimate is quite close to the real fee |
|
|
|
I am having the honour to announce 1 year of bitbattle.me!bitbattle.me is now one of the longest running dice sites, with a 100% clean history - no thefts, no scams, no complaints! This clearly deserves a celebration! Therefor I am happy to present the Anniversary Deal: 1% house edge discount!
House edge is reduced by 1% to an all-time low of 0.9%
This anniversary deal will end on 2013-11-7.
May the luck be with you |
|
|
|
This morning the backend was stuck for about 2 hours, so no bets could be accepted. Problem is fixed and all transactions that came in during that period are handled. Sorry for the inconvinience  |
|
|
|
|
As far as I remember the client will re-broadcast it's transactions regularly while they are not confirmed, so it will probably take a while but eventually it should propagate.
Can you provide the TransactionID?
|
|
|
|
|
@ASICSRUS: Jeez, you better stop online gambling.
|
|
|
|
Only 10 days left until the first anniversary! |
|
|
|
Just noticed that this thread started exactly 20 months ago! This feels like ages in the bitcoin world. Just look at the exchange rate at that time - around 5 USD |
|
|
|
Interesting idea, but isn't this quite risky? The moment the locked transaction gets lost the coins are gone, because the original private keys are already forgotten.
This would be cool if the locked transaction would be safe in the blockchain, but as this is not the case you need to have a real safe storage for the locked transaction in order to broadcast it when it's time has come.
The locked tx can be emailed / exported to the user before the private keys are deleted. The user can then broadcast this tx himself at a later date. Yes, but that's the point. User needs to manually store the tx in a safe place. Not the kind of a "fire-and-forget" action, instead user has to take exactly the same security consideration as with any offline wallet. |
|
|
|
|
Interesting idea, but isn't this quite risky? The moment the locked transaction gets lost the coins are gone, because the original private keys are already forgotten.
This would be cool if the locked transaction would be safe in the blockchain, but as this is not the case you need to have a real safe storage for the locked transaction in order to broadcast it when it's time has come.
|
|
|
|
|
Great site!
Feature request: It would be awesome if one could select which sources to draw into a chart. One line per exchange, all in the same timeframe. So you can see in one chart how the proces behave differently (or not) on the various exchanges.
|
|
|
|
|
I would be all in for supporting Gox through their troubles if they would be transparent and honest.
With the current way they handle the situation I can only recomend everybody to GTFO of it.
|
|
|
|
|
Show Posts
