is this kind of thing resolved automatically with "blockchain magic" or does satoshidice have to manually correct these things ? If the latter, it may explain the delays.
Something in between I think. After a few days Erik usually posts that the delay was caused by an error and that it has now been fixed and the problem won't happen again. ![Wink](https://bitcointalk.org/Smileys/default/wink.gif)
|
|
|
Now that there are lots of games running it might be better to show the results in reverse order, so that I don't have to keep scrolling to the bottom of the page to see the most recent results.
Maybe also by default only show the 25 (or whatever) most recent games, but offer a link that shows them all, or pages through them 25 at a time.
|
|
|
I'm currently seeing 855.9465 BTC worth of bets which haven't been paid out yet, with their pending payouts totalling 3839.90678494 BTC, for a net loss to the site of 2983.96028494 BTC.
That would put the site's overall profits after fees at around the 17000 BTC mark.
|
|
|
Incidentally, wagers that are double spends don't cost SatoshiDICE a thing, because even if they sent a payout for the WIN already the payout will not confirm either as it too will be a double spend.
What if I could double-spend just my losing bets? That would cost them plenty.
|
|
|
I'm still getting "You have reached the limit of daily withdraws. Please wait and try it again."
It would be nice if it could tell me how long I have to wait for the day to end. I have no idea what timezone the server uses.
"Please wait at least 5 hours and 23 minutes and try it again" for instance would make things clearer.
Good idea, I've added this. Thinking further about this, why even ask for a withdraw address and amount if I've already used my 10 withdraws for the day? You can tell as soon as I click 'withdraw' that I'm not going to be allowed to withdraw, so tell me then that I need to wait x hours, rather than asking for the details then denying my request. I finally managed to withdraw the 2 BTC you gifted me yesterday. I lost the 250 mBTC sign-up bonus while trying to 'clear' the 2 BTC bonus but that's still a decent result. Thanks again. ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
I see new icons on the home page after logging in. I clicked 'settings'. It told me: ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FS5Uj7.png&t=663&c=piAoxxf4MK8Lkg) I have an account. I'm logged in to it. It even shows my name and balance in the corner of the complaining screen.
|
|
|
I just hope they didn't lost too much, to declare bankruptcy and forfeit everyone winning payments. I notice they are doing all the little payments.
Notice that it's easy to pay out on a losing bet. All you need is the losing bet as the transaction input. You send part of it back to the losing player and the rest to a satoshidice change address. So it doesn't matter if the satoshidice wallet is full of inputs that will never confirm; that doesn't impact their ability to pay out losing bets. It does hinder their ability to pay out winners however. This imbalance means that if you only look at fully confirmed bet+payout pairs, you'll see mostly losing bets showing up. This is reflected in the graph of their profits over time. Notice that for the last day or two their profits have been pretty much straight up. Also notice that they're about 20,000 BTC in the black. That doesn't look like bankruptcy to me. ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FfxxsJ.png&t=663&c=UGxvYt3BK6wstw)
|
|
|
There are currently 1374 bets that have been confirmed which haven't had their payouts confirmed yet: http://pastebin.ca/2262402 (it's too big to include in this post - I never hit the 64000 byte post size limit before) It looks like SatoshiDice is being swamped by thousands of tiny bets which they're not able to deal with in a timely manner. The blockage was probably initially caused by a double-spend attempt, which can have a large knock-on effect: when you make a transaction using a double-spent bet as an input, all the outputs are doomed to never confirm. Each of the transactions which you subsequently make using any of those outputs are also doomed to never confirm. And so on. Before you know it you have a huge tree of payouts which eventually just vanish because they depend on a double-spent bet. Eventually some kind of a clean-up script will run at SatoshiDice and all the missing payouts will be redone. It kind of sucks that you're having to wait, but you're not alone...
|
|
|
The reward is only player-created bids? It says 0.011, but shouldn't it include the initial bid and be 0.021?
The reward is all the payments that get into the first block. In the case you're looking at, the first player-created bit got confirmed *before* the initial 0.1 bid! See http://blockchain.info/address/1Y4xaSKCVmRCxP5a9Lfp85SwNP4zocQCZ?filter=2I notice that the website is still linking to blockexplorer.com for the 'bid address' column. The above type of link is much nice - it only shows deposits from the given address, and is as a result clearer to read. Also, the table on the website doesn't list the 'initial bid' amount. That would be interesting to see. Also consider adding "start time" (or "game duration") and possibly "number of bids in winning block", "total number of bids", "value of late bids" (where the last 2 would possibly continue to rise after the game was over).
|
|
|
Very nice overnight profit for SatoshiDice! Results: 2012-Dec-01 09:51am (up to block 210468)
Address Target Should Win | #Bets | Win | Lose | Refunds | BTC In | BTC Out | Refund | Profit | RTP --------------------------------------------------------------------------------------------------------------------------------------------- 1dice1e6p 1 0.00002 | 49848 | 0 (0.00000) | 49353 | 495 | 304.56 | 0.01 | 55.46 | 304.54 | 0.006 1dice1Qf4 2 0.00003 | 2470 | 0 (0.00000) | 2366 | 104 | 38.30 | 0.00 | 12.94 | 38.30 | 0.005 1dice2pxm 4 0.00006 | 4100 | 0 (0.00000) | 4056 | 44 | 50.86 | 0.04 | 7.39 | 50.82 | 0.085 1dice2vQo 8 0.00012 | 5220 | 2 (0.00039) | 5173 | 45 | 81.46 | 16.08 | 5.65 | 65.37 | 19.744 1dice2WmR 16 0.00024 | 6457 | 1 (0.00016) | 6416 | 40 | 179.19 | 4.31 | 12.60 | 174.88 | 2.407 1dice2xkj 32 0.00049 | 7990 | 3 (0.00038) | 7975 | 12 | 487.77 | 303.43 | 1.29 | 184.34 | 62.208 1dice2zdo 64 0.00098 | 10144 | 10 (0.00099) | 10108 | 26 | 762.84 | 135.65 | 55.64 | 627.18 | 17.783 1dice37Ee 128 0.00195 | 12301 | 23 (0.00188) | 12217 | 61 | 1692.86 | 1293.35 | 48.26 | 399.50 | 76.401 1dice3jkp 256 0.00391 | 15410 | 69 (0.00448) | 15323 | 18 | 1882.77 | 2651.97 | 13.12 | -769.19 | 140.854 1dice4J1m 512 0.00781 | 21204 | 161 (0.00760) | 21029 | 14 | 3615.04 | 3448.95 | 9.35 | 166.08 | 95.406 1dice5wwE 1000 0.01526 | 54844 | 845 (0.01541) | 53985 | 14 | 11798.37 | 11104.86 | 1.80 | 693.51 | 94.122 1dice61SN 1500 0.02289 | 18402 | 442 (0.02403) | 17951 | 9 | 5966.30 | 6236.34 | 15.00 | -270.03 | 104.526 1dice6DPt 2000 0.03052 | 30796 | 971 (0.03154) | 29819 | 6 | 7535.71 | 6675.98 | 9.24 | 859.73 | 88.591 1dice6gJg 3000 0.04578 | 19621 | 909 (0.04636) | 18698 | 14 | 8129.39 | 9274.46 | 24.99 | -1145.07 | 114.086 1dice6GV5 4000 0.06104 | 24550 | 1511 (0.06156) | 23034 | 5 | 5433.14 | 4948.32 | 31.20 | 484.81 | 91.077 1dice6wBx 6000 0.09155 | 27480 | 2586 (0.09418) | 24871 | 23 | 11902.84 | 12514.52 | 7.01 | -611.68 | 105.139 1dice6YgE 8000 0.12207 | 112234 | 13752 (0.12256) | 98456 | 26 | 18575.24 | 16490.94 | 0.00 | 2084.30 | 88.779 1dice7EYz 12000 0.18311 | 33441 | 6205 (0.18568) | 27213 | 23 | 14120.32 | 14224.70 | 14.50 | -104.37 | 100.739 1dice7fUk 16000 0.24414 | 133629 | 32505 (0.24333) | 101079 | 45 | 83596.62 | 82693.14 | 566.80 | 903.48 | 98.919 1dice7W2A 24000 0.36621 | 99910 | 36699 (0.36759) | 63139 | 72 | 82029.49 | 82458.50 | 212.65 | -429.00 | 100.523 1dice8EMZ 32000 0.48828 | 717698 | 350555 (0.48879) | 366631 | 512 | 414599.87 | 410149.49 | 2923.44 | 4450.37 | 98.927 1dice97EC 32768 0.50000 | 290840 | 144966 (0.49883) | 145648 | 226 | 272018.12 | 265533.73 | 1709.79 | 6484.38 | 97.616 1dice9wcM 48000 0.73242 | 199310 | 146559 (0.73569) | 52653 | 98 | 190093.38 | 186524.60 | 704.59 | 3568.77 | 98.123 1dicec9k7 52000 0.79346 | 23051 | 18331 (0.79572) | 4706 | 14 | 33068.30 | 33014.19 | 1187.00 | 54.10 | 99.836 1dicegEAr 56000 0.85449 | 21373 | 18285 (0.85664) | 3060 | 28 | 32943.52 | 32546.33 | 400.00 | 397.19 | 98.794 1diceDCd2 60000 0.91553 | 17817 | 16313 (0.91610) | 1494 | 10 | 28568.17 | 28368.18 | 0.00 | 199.99 | 99.300 1dice9wVt 64000 0.97656 | 9489 | 9146 (0.98049) | 182 | 161 | 19556.65 | 19217.02 | 239.21 | 339.63 | 98.263 --------------------------------------------------------------------------------------------------------------------------------------------- small (bets < 4 BTC) | 1907767 | 770081 | 1135763 | 1923 | 460628.34 | 451091.90 | 165.33 | 9536.43 | 97.930 big (bets >= 4 BTC) | 61862 | 30768 | 30872 | 222 | 788402.87 | 778737.32 | 8103.70 | 9665.54 | 98.774 --------------------------------------------------------------------------------------------------------------------------------------------- | 1969629 | 800849 | 1166635 | 2145 | 1249031.21 | 1229829.22 | 8269.03 | 19201.98 | 98.463 ---------------------------------------------------------------------------------------------------------------------------------------------
SD Profit before fees: 19201.98823576 BTC (1.537%) Cumulative Fees Paid: 1163.93477500 BTC SD Profit after fees: 18038.05346076 BTC (1.444%) ---- Since Satoshi Dice started, there have been: Blockchain Tx: 6570728 : SatoshiDice Tx: 3640768 (55.4%) Blockchain MB: 2788.5 : SatoshiDice MB: 1490.1 (53.4%) ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FwA3Kw.png&t=663&c=7pRvqriA4aDzIw)
|
|
|
I see you've made some improvements, and approve. ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) I'm still getting "You have reached the limit of daily withdraws. Please wait and try it again." It would be nice if it could tell me how long I have to wait for the day to end. I have no idea what timezone the server uses. "Please wait at least 5 hours and 23 minutes and try it again" for instance would make things clearer. (Or I could just not hit the withdrawals page over and over in a greedy attempt to steal all your coins I suppose, then I wouldn't be having this problem... ![Wink](https://bitcointalk.org/Smileys/default/wink.gif) )
|
|
|
That's almost painful to watch. Poor kid has no idea. He can't be trolling them; can he?
|
|
|
Nice win! Yea playing a one man game though... ![Grin](https://bitcointalk.org/Smileys/default/grin.gif) It is easier to win when you're the only one playing... ![Wink](https://bitcointalk.org/Smileys/default/wink.gif) Have you considered what happens in the event of a blockchain reorganisation? It's not unheard of for some blocks that have been found to be replaced by completely different blocks with different sets of transactions. See http://blockchain.info/orphaned-blocks for a list of when this has happened. It happens on a daily basis, and can easily change the result of your game. History gets rewritten and the big payment that you thought hadn't made it into the first block now is in the first block... Edit: the obvious solution is to wait for 6 confirmations before paying out the winner. Reorgs almost never rewrite that much history. Can your script handle starting a new game while the previous one is still awaiting confirmations to be sure you got the correct winner and prize amount?
|
|
|
I would also: * display the user's balance on the home page - currently I can only see my balance if I go to the coinflip page * make it clear that part of the balance is considered a bonus which isn't available to be withdrawn until it has been played through; if there's a bonus to play through show that fact on the home screen. I had no idea what was going on when I was first trying to withdraw - it would allow me to withdraw 74 but not 75. Turns out that's because I had won a total of 74 chips, but I didn't understand that from the little information I was given. * make the 'heads' and 'tails' images clickable, rather than having me target a tiny radio button thingy. * put some cell padding around the items in the deposit table. the "Transaction ID" runs right into the date: ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FHEs4d.png&t=663&c=eu3IexInJ2A7jA) * what is that transaction ID anyway? Is that some kind of internal reference ID? I don't see myself ever using it when it's the bitcoin txid that I see in my wallet.
|
|
|
Dooglus, thank you very much for this detailed error report. This bug has been fixed now (the same kind as the first one) and you have got an additional 2000 m฿ bonus for your honesty.
Thanks! I'm going to make the INFO button clickable, which will display more information about the game.
Do you plan to make the clickable items visually different than the rest of the content? Currently it's hard to know what to do. Maybe make the clickable things look more traditionally like a button? shuffle:secret = hash (SHA256)
OK, I get it now, thanks. You have shuffled and decided how the coin is going to land before I even decide how much to bet, and that's what you're proving to me; that you didn't change your mind when you what side I picked. There's no proof that you decided how the coin would land in any fair way, just that you didn't change the result based on my choice and/or stake. Please note that you have the choice between heads and tails, so there isn't a way to cheat.
I hadn't noticed that I could chose. But even now I know that, you could still be arranging things so that 5% of all tosses land on the "edge" so I'm bound to lose. It's possible to get around that possibility, and prove to your users that you aren't cheating. See https://techblog.bitzino.com/2012-06-30-provably-fair-shuffling-through-cryptography.html for how bitZino does it by having both the casino and the user provide part of the seed used to shuffle.
|
|
|
Also: All requests can be done use GET or POST methods Can be done using?
|
|
|
a compromised future secret will compromise all further secrets from that point. That's confusing to me. It only makes sense if going back in time is going further. I think it would be clearer if you said "all previous secrets from that point" or, better, "all secrets before that point".
|
|
|
Thanks for all the effort in looking into this tiny problem. I went back thru my transactions, and sure enough, on the 25th I have an unmatched .01953848 transaction. That must be it finally clearing in. I still however have those unconfirmed transactions that should disappear. Do you know of the magic keystroke to get those to go away?
I don't know of a good way of removing unconfirmed transactions other than using the PyWallet program which is a little awkward to use. But if you want to try, there are instructions in the first post here: https://bitcointalk.org/index.php?topic=34028.0 See "Delete transactions from your wallet". Close down bitcoin and make a backup of your wallet before you try it.
|
|
|
To: satoshidice.com lessthan 00004 15990.789 1dice2pxmRZrtqBVzixvWnxsMa7wN2GCK Debit: -0.001 BTC To: satoshidice.com lessthan 32000 2.031 1dice8EMZmqKvrGE4Qc9bUFf9PX3xaYDp Debit: -0.01 BTC Transaction ID: b80ee0c2d01f40731a48bf0f5ca97004602a4357da4e2fd9fb3dac43b77818e0
If you take that transaction ID and search on blockchain.info for it like this: http://blockchain.info/search?search=b80ee0c2d01f40731a48bf0f5ca97004602a4357da4e2fd9fb3dac43b77818e0you get to see the 3 outputs. You'll see that all 3 are marked as 'spent', including the two satoshidice outputs: ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FLTGec.png&t=663&c=DsG_DIxDBR5Uow) That means they've processed the bets and payed you out. Click the two 'spent' links next to the two satoshidice bets to see how much they paid. The 0.001 bet to the long-shot address lost: ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FMRytV.png&t=663&c=ZxKZ3cR_wvlZIQ) and the 0.01 bet to the 50/50 address won: ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FbLmkO.png&t=663&c=3RGuj4G7hQsioA) So maybe you just didn't notice the payouts in your wallet? Or are you sure they're not there?
|
|
|
|