Topic: SatoshiDICE.com - The World's Most Popular Bitcoin Game - page 271. (Read 495799 times)
Tables have now been beautified, and users can select a row to highlight it (making it easier to see data in that row).
Probably a problem with the host. (needs some montoring so the site can display an "out of order" when this happens).
Fortunately, the wagers aren't lost anywhere, just that thing needs to get started back up for processing to resume.
Fortunately, the wagers aren't lost anywhere, just that thing needs to get started back up for processing to resume.
Absolutely correct. We have alarms in place but I've stopped just short of having them actually wake me up. We have made some great improvements in the resilience of the processing but there are still occasionally issues. I hope to get them ironed out in the next few weeks.
Regardless, at the very bottom of the main page there is a status indicator now. It shows the time in GMT of the last metrics reporting run and how many seconds ago that was. It should in general be between 0 and 120 seconds or so. If it goes longer, it means the processing is very busy or stalled in some way. If there is a problem, all transactions will be handled when it starts up again.
I wanted to go back and manually go through the motions of verifying a previous transaction, but I see it has rolled off the "recent' page.
There are 200 rows on that page, and my wager was about 28 hours prior.
In other words, that method wasn't built to accommodate the level of activity the site has already.
I know I can get the trx # from my client and build the URL for that manually, but clicking on a page is more convenient.
Is there anything that can be done so that the past N days (e.g. 10 days) of wagers are retained for review?
(or given and index with sequential numbering and an API to retrieve these at our leisure?)
There are 200 rows on that page, and my wager was about 28 hours prior.
In other words, that method wasn't built to accommodate the level of activity the site has already.
I know I can get the trx # from my client and build the URL for that manually, but clicking on a page is more convenient.
Is there anything that can be done so that the past N days (e.g. 10 days) of wagers are retained for review?
(or given and index with sequential numbering and an API to retrieve these at our leisure?)
I will be working on that this week. I was thinking of a search but a paginated view as you seem to be suggesting might work as well.
I see that fees are added to each payout transaction. In many instances where the wager was small, the fee paid on a payout for a losing wager is a higher amount than the payout.
That's gotta cut into the site's operating costs, to where some wagers place can never be serviced profitably?
That's gotta cut into the site's operating costs, to where some wagers place can never be serviced profitably?
Absolutely. The way I see it, the low min bets are for making players comfortable with the system with low risk (for the player). So yeah, we take a loss on those.
make sure they cant spam your site with tiny bets then.
You may have a competitor or a disgruntled user spam the site with tiny bets to attempt to drain your funds.
Will give the site a whirl tonight
, come on 65,000x win 
I see that fees are added to each payout transaction. In many instances where the wager was small, the fee paid on a payout for a losing wager is a higher amount than the payout.
That's gotta cut into the site's operating costs, to where some wagers place can never be serviced profitably?
That's gotta cut into the site's operating costs, to where some wagers place can never be serviced profitably?
Absolutely. The way I see it, the low min bets are for making players comfortable with the system with low risk (for the player). So yeah, we take a loss on those.
I see that fees are added to each payout transaction. In many instances where the wager was small, the fee paid on a payout for a losing wager is a higher amount than the payout.
That's gotta cut into the site's operating costs, to where some wagers place can never be serviced profitably?
That's gotta cut into the site's operating costs, to where some wagers place can never be serviced profitably?
Oooh ... brutal
Martingale strategy fail.
2012-04-28 19:19:27 lessthan 32768 b95c0344 1f71ff4e 6.20000000 LOSE 0.02535400 50530
2012-04-28 19:18:33 lessthan 32768 4f0197ea eddb1551 3.10000000 LOSE 0.01267700 36539
2012-04-28 19:16:53 lessthan 32768 b94a4506 49eeb4c1 1.50000000 LOSE 0.00613403 35076
2012-04-28 19:16:11 lessthan 32768 8e34c3bd 93ec8faf 0.70000000 LOSE 0.00286254 54030
There needs to be an IRC channel for this.
- http://webchat.freenode.net/?channels=#satoshidice
With a bot that echoes each wager, real-time.
Heh, sorry but all wagers are sent to a set of static addresses ... and the Blockchain doesn't forget.
Martingale strategy fail.
2012-04-28 19:19:27 lessthan 32768 b95c0344 1f71ff4e 6.20000000 LOSE 0.02535400 50530
2012-04-28 19:18:33 lessthan 32768 4f0197ea eddb1551 3.10000000 LOSE 0.01267700 36539
2012-04-28 19:16:53 lessthan 32768 b94a4506 49eeb4c1 1.50000000 LOSE 0.00613403 35076
2012-04-28 19:16:11 lessthan 32768 8e34c3bd 93ec8faf 0.70000000 LOSE 0.00286254 54030
There needs to be an IRC channel for this.
- http://webchat.freenode.net/?channels=#satoshidice
With a bot that echoes each wager, real-time.
I'm not sure we want to retain wager records forever, for a number of reasons.
Heh, sorry but all wagers are sent to a set of static addresses ... and the Blockchain doesn't forget.
From the Recent Bets looks like 44 transactions got processed all at once (when it restarted) so you should see your payouts now.
- http://www.satoshidice.com
I also notice that using a client where the wallet that hasn't caught up to the latest block won't show some payout transactions when the inputs for them cannot be verified yet due to the blockchain download not being current enough.
- http://www.satoshidice.com
I also notice that using a client where the wallet that hasn't caught up to the latest block won't show some payout transactions when the inputs for them cannot be verified yet due to the blockchain download not being current enough.
i would prefer if what i bet on worked as advertised
... where is the interest on the time i waited?
... where is the interest on the time i waited?
6/21 have shown up - the rest are just... missing
Ya, the last transaction listed in the Recent Bets / history was several hours ago:
Details 2012-04-28 08:07:48
Probably a problem with the host. (needs some montoring so the site can display an "out of order" when this happens).
Fortunately, the wagers aren't lost anywhere, just that thing needs to get started back up for processing to resume.
The history shows only about 12 hours worth of history now. Two hundred bets in 12 hours.
Instant Blockchain-based wagering.
Can you say ...
Bitcoin has found its killer app?
I wonder what Satoshi is thinking right about now.
(I'm envisioning something along the lines of ...
"I gave you fire, and you piss on it because you like the pretty colored smoke clouds doing that makes?
A pox on all your houses!" [then puts in a 1 million BTC market SELL order]
). haven't gotten a payment nor has it shown up on the site, a few different transactions for about the last 50 minutes...
Does it show up in the blockchain?
- http://www.blockchain.info
If not, are the inputs from a coin that hasn't confirmed yet? A small amount? No fee?
Those conditions will cause the payment to not only not end up getting mined right away, but they will cause the payemnt to not even get relayed by the nodes. (It looks "spammy" to them.) If this is the case, it will take a while for the transaction to get processed.
i have 14+ confirmations on all of my "sent", some of them have come in now, but still more than half just not showing up
6/21 have shown up - the rest are just... missing
haven't gotten a payment nor has it shown up on the site, a few different transactions for about the last 50 minutes...
Does it show up in the blockchain?
- http://www.blockchain.info
If not, are the inputs from a coin that hasn't confirmed yet? A small amount? No fee?
Those conditions will cause the payment to not only not end up getting mined right away, but they will cause the payemnt to not even get relayed by the nodes. (It looks "spammy" to them.) If this is the case, it will take a while for the transaction to get processed.
haven't gotten a payment nor has it shown up on the site, a few different transactions for about the last 50 minutes...
Hehehe, someone just broke your toy here
http://satoshidice.com/full.php?tx=167d58f4deb529afec5e1505f34387ac13a63147b801797a966742b7d7c49eed
http://satoshidice.com/full.php?tx=167d58f4deb529afec5e1505f34387ac13a63147b801797a966742b7d7c49eed
Maybe it's even possible to publish the secrets in the blockchain.
Or a new use for Namecoin.
Maybe it's even possible to publish the secrets in the blockchain.
I'm not sure we want to retain wager records forever, for a number of reasons. But, should probably at least be a week or so. I'll put this on our todo list.
I would have thought keeping records would be a good idea! If you kept track of all tx's and the secret as well. It helps prove your sites honesty. I wouldn't worry about the privacy part since the address can be looked up anyways in blockexplorer. I wanted to go back and manually go through the motions of verifying a previous transaction, but I see it has rolled off the "recent' page.
There are 200 rows on that page, and my wager was about 28 hours prior.
In other words, that method wasn't built to accommodate the level of activity the site has already.
I know I can get the trx # from my client and build the URL for that manually, but clicking on a page is more convenient.
Is there anything that can be done so that the past N days (e.g. 10 days) of wagers are retained for review?
(or given and index with sequential numbering and an API to retrieve these at our leisure?)
There are 200 rows on that page, and my wager was about 28 hours prior.
In other words, that method wasn't built to accommodate the level of activity the site has already.
I know I can get the trx # from my client and build the URL for that manually, but clicking on a page is more convenient.
Is there anything that can be done so that the past N days (e.g. 10 days) of wagers are retained for review?
(or given and index with sequential numbering and an API to retrieve these at our leisure?)
I'm not sure we want to retain wager records forever, for a number of reasons. But, should probably at least be a week or so. I'll put this on our todo list.
I wanted to go back and manually go through the motions of verifying a previous transaction, but I see it has rolled off the "recent' page.
There are 200 rows on that page, and my wager was about 28 hours prior.
In other words, that method wasn't built to accommodate the level of activity the site has already.
I know I can get the trx # from my client and build the URL for that manually, but clicking on a page is more convenient.
Is there anything that can be done so that the past N days (e.g. 10 days) of wagers are retained for review?
(or given and index with sequential numbering and an API to retrieve these at our leisure?)
There are 200 rows on that page, and my wager was about 28 hours prior.
In other words, that method wasn't built to accommodate the level of activity the site has already.
I know I can get the trx # from my client and build the URL for that manually, but clicking on a page is more convenient.
Is there anything that can be done so that the past N days (e.g. 10 days) of wagers are retained for review?
(or given and index with sequential numbering and an API to retrieve these at our leisure?)
Jump to: