Well i havent been paid for a 2 btc bet i won over an hour ago. Still says unknown but has paid a bunch of others bets i have done. What do I do? This game has taken enough from me i dont need to take shit i also won.
It happens occasionally. It doesn't appear that making a fuss helps get it resolved any quicker unfortunately, though you could try that. All bets get paid out eventually, but I've seen it take 2 or 3 days before.
|
|
|
We just pushed a bunch of fixes for all the issues you've been bringing up Dooglus. I also added another 0.25 BTC to your account to thank you for all the help you've provided us. This offer stands for anyone else too!
Thanks for the 250k uBTC. I thought I had found another bug - maybe one to keep to myself for a bit. I got my balance up to 1.6 BTC, placed a largish bet on the roulette table, but then clicked 'cash out' before spinning the wheel. My balance went to 1.85 BTC. I figured you had accidentally added the placed-but-not-spun bet to my balance twice. Then I checked the 'deposit' page and saw it was another thank you deposit. One issue this brought up for me was that the timestamp on the deposits is in UTC. I thought UTC was 8 hours ahead of here, which would have made the 0.25 deposit just about 61 minutes ago, in which case I was wondering why you hadn't posted about it. But I guess UTC is only 7 hours ahead of here, and you had made the 0.25 BTC deposit into my account before composing your post here. What I'm trying to say is I'd like to see all timestamps in localtime, not UTC. Maybe let me pick a timezone, or maybe trust that my browser knows what timezone I'm in, I don't really care which.
|
|
|
BTCDice works using the UTC timestamp from transaction to determine day of transaction (in UTC) and then process using secret of that day (in UTC).
Transactions don't have timestamps though. You client may make a note of the time that it first saw a particular transaction, but my client may put a different timestamp on it. I don't think there's any way we can safely agree on the exact timestamp of a transaction, since it's not part of the transaction itself. All we can agree upon is the timestamp of the block that includes it.
|
|
|
You're not going to believe this, but I just shut down Linux and booted into Windows 7. My laptop came with Windows 7, but I've never used it before other than for 5 minutes to see what it looked like. I went to pmpoker.com and downloaded the .exe installer again, and ran it. I logged in to my dooglus account, and everything happened the same as in WINE. First I got an access violation error, then a bunch of bigger messages with JSON in them. Here's a screenshot: Note the bog standard ACER wallpaper - it's a real OEM Windows 7 install that came pre-installed on the laptop because I was too lazy to try to find a "No OS" laptop this time. So maybe the issue is with my pmpoker account, but it's definitely NOT with WINE!
|
|
|
I guess I should try something else that I know used to work great in WINE and see how that works now. It that's messed up too then I should stop posting here, since it's clearly a WINE issue.
I just installed PokerStars from an old .exe I had lying around. I ran the .exe in WINE, it told me there was a newer version available, offered to download it, downloaded it, installed it, let me log in, and everything looks fine: So WINE still works for me like it used to, except not with pmpoker. I hope somebody makes an HTML5 poker site some day, using the same kind of technology as http://bitzino.com/ uses. Those guys know how to make a gambling site that works for everyone. No need for Windows, Flash, etc. Just use your browser, and it just works.
|
|
|
Hmm. So, I'm not the only one with Wine problems?
I installed Wine on Fedora today. To be clear, I've never used Wine before. I tried opening PM Poker and it would make it as far as the log in screen, where it asks me whether I want to log in as guest or as a real user. Then I clicked guest and that was it. Nothing else loaded. I assumed Wine was just junk and so I uninstalled Wine. Maybe I shouldn't be so quick to judge Wine if it's actually PM Poker software. Although I am worried about getting malware through Wine. Can anybody alleviate my fears about malware through Wine?
I've had good success with WINE in the past. Some programs work 100% fine with it, and some don't work at all. What's weird is that pmpoker worked great in WINE until yesterday... I guess I should try something else that I know used to work great in WINE and see how that works now. It that's messed up too then I should stop posting here, since it's clearly a WINE issue. The thing is, I expect lots of people with Bitcoins don't use Windows. Windows is notorious for being targeted by viruses and other malware, so it makes sense to avoid it and use something more secure if you're going to be dealing with Bitcoins. I'm not sure a Windows-only Bitcoin poker site is going to fly at the moment. I'm no expert on malware, but I would expect it's less likely to be able to thrive in a WINE environment than on a real Windows box. Specially crafted programs could probably cause you some trouble though. I believe programs running in WINE can see your whole filesystem, not just your ~/.wine.
|
|
|
I'll try deleting my ~/.wine folder and reinstalling pmpoker from scratch.
I did that. I re-downloaded the .exe file from the pmpoker website and ran it in WINE after deleting my .wine folder (where the Windows C: drive is stored, etc). After installing, pmpoker downloaded over 5MB of "updates", which is bigger than the installer itself. But that's a separate issue. Once it had updated, it let me type my username and password, and then went crazy, flashing up error boxes quickly. I moved some of them around so you can see a few of them: I wonder if I can go back to the previous version of WINE somehow...
|
|
|
tldr: pmpoker doesn't want to work with wine, but it used toI don't know what's going on today, but I'm unable to play pmpoker at all. I get all kinds of error dialogs popping up which stop me from being able to play. Earlier today I was getting this: followed by an awful lot of beeping. It was as if my actions (fold, raise, etc) were being ignored and the beeping was trying to get me to act, when I had already acted, and the buttons to act with has already disappeared. I signed up for 3 tournaments this morning, and couldn't play in any of them for more than a few hands before the problems started. I did manage to win 25 mBTC in each of them though by coming 3rd or 4th without winning a hand. There are few enough players that you can get in the money without playing at the moment - so it's worth signing up just for that! This afternoon I just tried again, and now I'm getting different errors: These error boxes appear faster than I can close them, making play impossible. I run Ubuntu Linux, and use WINE to run pmpoker, since there doesn't seem to be a Linux client available for it. This has worked flawlessly until yesterday (well, as flawlessly as on Windows, I expect - I've had small issues with it, but nothing like this). I updated Ubuntu from version 12.04 to 12.10 yesterday, so that may be the root cause of the problem. The new Ubuntu may have a different version of WINE. I just checked. Here are the versions I've installed: 2012-07-23 18:00:47 status installed wine 1.4-0ubuntu4 2012-07-26 15:25:17 status installed wine 1.4-0ubuntu4.1 2012-10-22 19:40:56 status installed wine:amd64 1.4.1-0ubuntu1 So it went from 1.4.0 to 1.4.1 with the new Ubuntu yesterday. I'll try deleting my ~/.wine folder and reinstalling pmpoker from scratch.
|
|
|
What im saying is it doesnt matter what the secret number is since it has to correspond with the hash. The hash is after you place the bet. Obviously. Where does this hash come from? A random draw?
I think you're confusing two hashes. There's: * The hash of the day's secret number. It was published months ago and won't change. * The hash of your bet transaction, also known as the transaction ID. It is created (by your client, not by SatoshiDice) when you make a payment. It doesn't change. Ok im so conufsed with this then. How can i chose my transaction ID? All i do is open my wallet and copy and paste the address in which i want to send the corresponding bet to. Where is it that im chosing the ID? CAn you explain step by step what happens right before i place my bet so I can understand it more?
You get to pick your transaction ID if you want to, as follows: 1. back up your wallet.dat file 2. turn off your Internet connection 3. tell your wallet to send a bet to SD 4. check the transaction ID 5. if you don't like it, quit the wallet program, restore your wallet.dat from the backup, restart the wallet program, and go back to step 3, but add 1 satoshi to the bet amount. that will cause a completely different transaction ID to be used 6. turn your Internet connection back on 7. wait for the wallet to send the transaction (only the most recent one, whose txid you liked) out to the network There's no point doing any of this if you don't know the daily secret, because you can't tell with txid values to "like" - you would want to like just the ones that are going to win, but you can't tell that without the secret, which you won't know until tomorrow. You usually just create a transaction and instantly broadcast it, but using the steps above it's possible to check the txid before broadcasting it, and delete (by restoring a backup) the transaction so nobody but you ever knows you made it.
|
|
|
Results: 2012-Oct-23 10:41am (up to block 204627)
Address Target Should Win | #Bets | Win | Lose | Refunds | BTC In | BTC Out | Refund | Profit | RTP -------------------------------------------------------------------------------------------------------------------------------------------- 1dice1e6p 1 0.00002 | 29747 | 0 (0.00000) | 29362 | 385 | 219.97 | 0.01 | 33.93 | 219.95 | 0.009 1dice1Qf4 2 0.00003 | 1993 | 0 (0.00000) | 1914 | 79 | 28.62 | 0.00 | 9.28 | 28.62 | 0.006 1dice2pxm 4 0.00006 | 3045 | 0 (0.00000) | 3007 | 38 | 39.11 | 0.03 | 4.42 | 39.08 | 0.080 1dice2vQo 8 0.00012 | 3713 | 2 (0.00055) | 3667 | 44 | 67.20 | 16.06 | 5.65 | 51.13 | 23.907 1dice2WmR 16 0.00024 | 5212 | 1 (0.00019) | 5173 | 38 | 153.33 | 4.28 | 8.40 | 149.05 | 2.793 1dice2xkj 32 0.00049 | 6928 | 3 (0.00043) | 6913 | 12 | 454.97 | 303.33 | 1.29 | 151.63 | 66.671 1dice2zdo 64 0.00098 | 8649 | 8 (0.00093) | 8619 | 22 | 711.61 | 124.51 | 55.64 | 587.09 | 17.498 1dice37Ee 128 0.00195 | 10741 | 19 (0.00178) | 10666 | 56 | 1636.32 | 1274.70 | 44.25 | 361.62 | 77.900 1dice3jkp 256 0.00391 | 11992 | 55 (0.00459) | 11923 | 14 | 1835.10 | 2621.89 | 13.11 | -786.79 | 142.875 1dice4J1m 512 0.00781 | 18501 | 141 (0.00763) | 18349 | 11 | 3478.85 | 3182.70 | 9.35 | 296.15 | 91.487 1dice5wwE 1000 0.01526 | 38160 | 581 (0.01523) | 37566 | 13 | 9814.92 | 9393.80 | 1.80 | 421.11 | 95.709 1dice61SN 1500 0.02289 | 17253 | 405 (0.02349) | 16840 | 8 | 5571.65 | 5735.10 | 15.00 | -163.44 | 102.933 1dice6DPt 2000 0.03052 | 24954 | 787 (0.03154) | 24163 | 4 | 6340.89 | 5951.36 | 9.24 | 389.53 | 93.857 1dice6gJg 3000 0.04578 | 17760 | 825 (0.04647) | 16927 | 8 | 7665.19 | 9067.14 | 24.99 | -1401.94 | 118.290 1dice6GV5 4000 0.06104 | 17517 | 1094 (0.06247) | 16419 | 4 | 5064.18 | 4664.74 | 31.20 | 399.43 | 92.113 1dice6wBx 6000 0.09155 | 23549 | 2206 (0.09375) | 21324 | 19 | 10872.82 | 10977.80 | 7.01 | -104.97 | 100.965 1dice6YgE 8000 0.12207 | 94669 | 11624 (0.12282) | 83022 | 23 | 12836.25 | 11281.69 | 0.00 | 1554.56 | 87.889 1dice7EYz 12000 0.18311 | 23952 | 4471 (0.18677) | 19467 | 14 | 9303.66 | 9540.56 | 14.50 | -236.89 | 102.546 1dice7fUk 16000 0.24414 | 105430 | 25724 (0.24405) | 79682 | 24 | 63011.70 | 61060.32 | 347.79 | 1951.37 | 96.903 1dice7W2A 24000 0.36621 | 73925 | 27154 (0.36756) | 46723 | 48 | 46277.60 | 46263.11 | 212.64 | 14.49 | 99.969 1dice8EMZ 32000 0.48828 | 633365 | 309298 (0.48869) | 323618 | 449 | 364264.42 | 361212.08 | 2173.41 | 3052.34 | 99.162 1dice97EC 32768 0.50000 | 221931 | 110733 (0.49938) | 111009 | 189 | 211287.81 | 208237.95 | 1295.22 | 3049.85 | 98.557 1dice9wcM 48000 0.73242 | 166431 | 122429 (0.73597) | 43922 | 80 | 164390.76 | 162577.17 | 467.98 | 1813.59 | 98.897 1dicec9k7 52000 0.79346 | 16221 | 12912 (0.79640) | 3301 | 8 | 24684.02 | 24500.58 | 400.00 | 183.43 | 99.257 1dicegEAr 56000 0.85449 | 15254 | 13063 (0.85766) | 2168 | 23 | 22331.64 | 22038.86 | 400.00 | 292.78 | 98.689 1diceDCd2 60000 0.91553 | 7492 | 6860 (0.91650) | 625 | 7 | 16770.74 | 16829.78 | 0.00 | -59.03 | 100.352 1dice9wVt 64000 0.97656 | 8073 | 7766 (0.97994) | 159 | 148 | 16621.65 | 16340.57 | 239.21 | 281.08 | 98.309 -------------------------------------------------------------------------------------------------------------------------------------------- small (bets < 4 BTC) | 1555360 | 632443 | 921358 | 1559 | 385480.23 | 377613.76 | 152.08 | 7866.47 | 97.959 big (bets >= 4 BTC) | 51097 | 25718 | 25170 | 209 | 620254.88 | 615586.46 | 5673.35 | 4668.41 | 99.247 -------------------------------------------------------------------------------------------------------------------------------------------- | 1606457 | 658161 | 946528 | 1768 | 1005735.12 | 993200.23 | 5825.44 | 12534.89 | 98.754 --------------------------------------------------------------------------------------------------------------------------------------------
SD Profit before fees: 12534.89025942 BTC (1.246%) Cumulative Fees Paid: 809.38590000 BTC SD Profit after fees: 11725.50435942 BTC (1.166%) ---- Since Satoshi Dice started, there have been: Blockchain Tx: 5393009 : SatoshiDice Tx: 2984165 (55.3%) Blockchain MB: 2263.8 : SatoshiDice Tx: 1218.0 (53.8%)
|
|
|
But that proves nothing. They can pick any number they want with any hash they want. You place your bet they use some hash that will screw you.
You're not getting it. They picked all the daily secrets before starting operations, and published all the hashes then too. So the day after you bet, they reveal the secret they used, and you can verify that its hash matches the hash they published months ago. That means they used the secret they made up months ago (or they've cracked the hash, in which case there's much bigger money to be made elsewhere). In addition to that, they use the same secret for everyone - they only use one secret per day. So even if they did have some way of switching secrets 'at the last minute', they'd have to find one that screwed you, but which also didn't change the result of any of the bets they'd already processed that day. If I was you I would read up on how it works and see if you can think of any way they could be cheating. It's easy to say "they can pick any number they want" when you don't understand how things work. But if you can make such a statement once you understand the mechanics of it, that would be interesting.
|
|
|
This game robs me steady lol. ITs alwasy throwing out 61000 or whatever when i do large bets with under 60000. I dont care what anyone says its rigged. Show me that its not rigged when I place my bet. IT sees my bet and address. How does it come up with the number when I push send money? IT doesnt come up wit hthe number before I bet obviously.
Click the 'verification' link in the top right corner of their site to read about how they pick the number. In short it goes like this: * at the dawn of time, they picked a random 'secret' number for each day, and published the hash of each secret number * when they receive your bet transaction, they use that day's secret and your bet's transaction ID to make your magic number. this is done using a well known, published algorithm. you could do it yourself if you knew their secret * at the end of the day, they publish that day's secret, and start using the next day's secret So a day after you place your bet, they publish the secret they used. You can check that the hash of the secret matches the hash they showed you in advance (so you can be sure they didn't make up a special secret just to make your bet lose) and you can also run the algorithm that combines the secret with your transaction id and check that the magic number they gave you is right.
|
|
|
dooglus,
You should consider a career as a software QA person.
Ew, that sounds like work. In other news, I found another annoyance. I have a bet of 2000 on a red. I want to change it to 2100, so I click the existing 2000 bet, click between the 2nd and 3rd digit of the 2000, moving the cursor there: then hit backspace to delete the first 0: and finally type '1' to insert a 1 where the first '0' used to be: As you can see, hitting backspace moves the cursor to the end of the bet amount, so when I type '1' I end up with 2001 and not 2100. Almost everything I do moves the cursor to the end of the text field, which is kind of annoying, and makes it hard to edit the bet amount. It's easier to just delete it and type the whole new value from scratch. Edit: I discovered I can change 2000 to 2100 by selecting the 1st '0' by dragging the mouse over it: and then typing a '1': It still moves the text cursor to the end of the amount, which looks weird, but at least now I can make single-digit changes without having to retype the whole amount. Edit2: note that the "bet per click" box has none of these problems. The cursor keys work correctly there, and I am free to edit the number in the manner to which I have become accustomed on every other site on the web.
|
|
|
I'd recommend bitZino too, and I don't have a referral link to push at you. Every game is provably fair - they shuffle the deck, then effectively allow you to cut it before they deal the hand, so the site itself doesn't know and can't control what cards (or dice rolls, or roulette numbers) are going to come out, since it's decided by the player's "cut". On top of that, the games all just work in your browser. No download required, and no Flash plugin required. All just pure HTML5 goodness. It's the only place I know that has all 3 of: * provably fair (like strike sapphire isn't - they publish the shuffles only well after you play, no hash magic before you play) * fun (like satoshidice isn't - it's like there's no game, just winning or losing) * always pays out when you win (like bitjack21 doesn't - they invented 'provably fair' but seem to have trouble paying out)
|
|
|
This guy is awesome, sealswithclubs is slowly going down, the admin has turned into a asshole and let his fame on the internet go to his head, whether this guy does the same thing, i don't know, but he is really putting effort into this, not just buying some shitty rigged software, he put alot in and i hope he gets alot out. Is it perfect? no, but it can only get better, right? no? yes.
That seems unfair. I've seen nothing but good from freemoney, and seals is a good poker site. It's good to see pmpoker starting to put up some competition but I think it's fair to say the software has some way to go before it's as nice to play as the sealswithclubs software. (And that's still miles behind the big companies' clients).
|
|
|
Yes, payments have been processed and sent.
You didn't update the balances like you usually do. And it looks like last week you updated the balances, but not the date of the last update.
|
|
|
* play on a site which allows you to place bets against other players, rather than against the house. spot good value bets and profit from them. . .
I believe that this example is called "arbitrage" and is occasionally used in sports betting (or other gambling where the payoff odds on the same event can differ between multiple bookmakers). I think if you're placing two complimentary bets which cancel each other out, leaving you a guaranteed profit, that's arbitrage. If you find a site that's offering a 10-1 payout for an event which you are pretty sure will happen around 50% of the time, that's not arbitrage; that's just taking advantage of someone estimating the true odds incorrectly.
|
|
|
Bitcoind provides a "time" and "timereceived" field for each transaction, even before the block clears... I thought.
Yes, but there's no way you can prove whether the site owner's bitcoind received the transaction today or tomorrow. The received time is potentially different for each bitcoin node.
|
|
|
Results: 2012-Oct-22 12:25pm (up to block 204500)
Address Target Should Win | #Bets | Win | Lose | Refunds | BTC In | BTC Out | Refund | Profit | RTP -------------------------------------------------------------------------------------------------------------------------------------------- 1dice1e6p 1 0.00002 | 29145 | 0 (0.00000) | 28760 | 385 | 218.99 | 0.01 | 33.93 | 218.97 | 0.009 1dice1Qf4 2 0.00003 | 1985 | 0 (0.00000) | 1906 | 79 | 28.51 | 0.00 | 9.28 | 28.51 | 0.006 1dice2pxm 4 0.00006 | 3038 | 0 (0.00000) | 3000 | 38 | 39.10 | 0.03 | 4.42 | 39.07 | 0.080 1dice2vQo 8 0.00012 | 3706 | 2 (0.00055) | 3660 | 44 | 67.19 | 16.06 | 5.65 | 51.13 | 23.909 1dice2WmR 16 0.00024 | 5204 | 1 (0.00019) | 5165 | 38 | 153.12 | 4.28 | 8.40 | 148.84 | 2.797 1dice2xkj 32 0.00049 | 6921 | 3 (0.00043) | 6906 | 12 | 454.87 | 303.33 | 1.29 | 151.53 | 66.686 1dice2zdo 64 0.00098 | 8614 | 8 (0.00093) | 8584 | 22 | 705.80 | 124.49 | 55.64 | 581.30 | 17.639 1dice37Ee 128 0.00195 | 10733 | 19 (0.00178) | 10658 | 56 | 1636.30 | 1274.70 | 44.25 | 361.59 | 77.901 1dice3jkp 256 0.00391 | 11978 | 55 (0.00460) | 11909 | 14 | 1834.04 | 2621.89 | 13.11 | -787.84 | 142.957 1dice4J1m 512 0.00781 | 18456 | 141 (0.00764) | 18304 | 11 | 3476.71 | 3182.70 | 9.35 | 294.01 | 91.543 1dice5wwE 1000 0.01526 | 37667 | 574 (0.01524) | 37080 | 13 | 9803.34 | 9385.66 | 1.80 | 417.68 | 95.739 1dice61SN 1500 0.02289 | 17235 | 405 (0.02351) | 16822 | 8 | 5570.70 | 5735.10 | 15.00 | -164.39 | 102.951 1dice6DPt 2000 0.03052 | 24942 | 787 (0.03156) | 24151 | 4 | 6340.01 | 5951.35 | 9.24 | 388.65 | 93.870 1dice6gJg 3000 0.04578 | 17734 | 825 (0.04654) | 16901 | 8 | 7663.53 | 9067.14 | 24.99 | -1403.60 | 118.315 1dice6GV5 4000 0.06104 | 17509 | 1093 (0.06244) | 16412 | 4 | 5063.18 | 4651.14 | 31.20 | 412.03 | 91.862 1dice6wBx 6000 0.09155 | 23529 | 2204 (0.09375) | 21306 | 19 | 10870.76 | 10976.71 | 7.01 | -105.95 | 100.975 1dice6YgE 8000 0.12207 | 94015 | 11538 (0.12276) | 82454 | 23 | 12700.25 | 11087.65 | 0.00 | 1612.59 | 87.303 1dice7EYz 12000 0.18311 | 23912 | 4465 (0.18684) | 19433 | 14 | 9301.01 | 9538.68 | 14.50 | -237.67 | 102.555 1dice7fUk 16000 0.24414 | 104553 | 25512 (0.24407) | 79017 | 24 | 62112.17 | 60088.74 | 347.79 | 2023.42 | 96.742 1dice7W2A 24000 0.36621 | 73441 | 26994 (0.36780) | 46399 | 48 | 45723.28 | 45766.74 | 212.64 | -43.45 | 100.095 1dice8EMZ 32000 0.48828 | 624588 | 305073 (0.48879) | 319066 | 449 | 362686.17 | 359481.01 | 2173.41 | 3205.15 | 99.116 1dice97EC 32768 0.50000 | 221522 | 110528 (0.49937) | 110805 | 189 | 210850.95 | 207801.39 | 1295.22 | 3049.55 | 98.554 1dice9wcM 48000 0.73242 | 165453 | 121707 (0.73595) | 43666 | 80 | 163726.91 | 161883.15 | 467.98 | 1843.76 | 98.874 1dicec9k7 52000 0.79346 | 15931 | 12693 (0.79715) | 3230 | 8 | 24588.99 | 24405.90 | 400.00 | 183.08 | 99.255 1dicegEAr 56000 0.85449 | 15142 | 12977 (0.85832) | 2142 | 23 | 22244.83 | 21952.29 | 400.00 | 292.54 | 98.685 1diceDCd2 60000 0.91553 | 7463 | 6833 (0.91644) | 623 | 7 | 16651.10 | 16706.46 | 0.00 | -55.36 | 100.333 1dice9wVt 64000 0.97656 | 8053 | 7747 (0.98001) | 158 | 148 | 16608.02 | 16326.98 | 239.21 | 281.03 | 98.308 -------------------------------------------------------------------------------------------------------------------------------------------- small (bets < 4 BTC) | 1541572 | 626569 | 913444 | 1559 | 383252.35 | 375380.61 | 152.08 | 7871.73 | 97.946 big (bets >= 4 BTC) | 50897 | 25615 | 25073 | 209 | 617867.60 | 612953.09 | 5673.35 | 4914.50 | 99.205 -------------------------------------------------------------------------------------------------------------------------------------------- | 1592469 | 652184 | 938517 | 1768 | 1001119.95 | 988333.71 | 5825.44 | 12786.24 | 98.723 --------------------------------------------------------------------------------------------------------------------------------------------
SD Profit before fees: 12786.24230857 BTC (1.277%) Cumulative Fees Paid: 802.34655000 BTC SD Profit after fees: 11983.89575857 BTC (1.197%) ---- Since Satoshi Dice started, there have been: Blockchain Tx: 5355856 : SatoshiDice Tx: 2958680 (55.2%) Blockchain MB: 2247.2 : SatoshiDice Tx: 1207.6 (53.7%)
|
|
|
What's going on here? "Your bitcoin deposit address: Available balance". It doesn't tell me my deposit address. Clicking "Or play with play money" then "play with bitcoins" fixed the problem.
|
|
|
|