The "lessthan 64000" bet has a maximum bet of -154.5618 BTC. If I bet negative bitcoins, does the house have a -3% edge? ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FuzOYo.png&t=663&c=z-_QzP2Z10fCSQ) Also, the banner at the top of the page still says "over 98% breakeven odds", which is apparently no longer true.
|
|
|
Thanks dooglus. I've been super busy and I accidentally deleted my most-recent updates to that script, and didn't feel like reimplementing it. I've been too busy trying to get out the next version of Armory.
You got the interpretation right: looks like SD is taking a really long time to process bets so there's a lot of unreturned bets piling up.
I've not checked, but maybe it's not that they're not processing them, but that miners can't/won't keep up? Either way it would show up the same on the blockchain I think.
|
|
|
It looks like the 'Unreturned' amount needs to come out of the profits, meaning the site is still 200 BTC down. This explains the increase in the house edge, I guess. Here's how I think the picture really looks: Total Bets Made: 543412 Cumulative Wagers: 195424.98368132 BTC Cumulative Rewards: 193333.06261702 BTC Cumulative Fees Paid: 269.38745000 BTC Cumulative Unreturned: 2038.08327919 BTC ---- SD Profit on Completed Bets : -215.54966489 BTC ---- Since Satoshi Dice started, there have been: Blockchain Tx: 1509892 : SatoshiDice Tx: 1010485 (66.9%) Blockchain MB: 641.5 : SatoshiDice Tx: 409.8 (63.9%)
|
|
|
Here's the latest output: Total Bets Made: 543412 Cumulative Wagers: 195424.98368132 BTC Cumulative Rewards: 193333.06261702 BTC Cumulative Fees Paid: 269.38745000 BTC Cumulative Unreturned: 2038.08327919 BTC ---- SD Profit/Loss From Games: 2091.92106430 BTC SD Profit/Loss With Fees: 1822.53361430 BTC
I don't know if that means they're up 2091 BTC but owe 2038 BTC in unreturned bets, or whether the 2091 BTC is profit.
|
|
|
Here's the latest output: Results: 2012-Jun-22 12:50pm
Address Target Should Win | #Bets | Win | Lose | Refunds | Accounted-for ---------------------------------------------------------------------------------------------------------------------- 1dice1e6p 1 0.00002 | 4941 | 0 (0.00000) | 4634 (1.00000) | 198 (0.04273) | (0.978) 1dice1Qf4 2 0.00003 | 635 | 0 (0.00000) | 470 (1.00000) | 59 (0.12553) | (0.833) 1dice2pxm 4 0.00006 | 1152 | 0 (0.00000) | 1016 (1.00000) | 30 (0.02953) | (0.908) 1dice2vQo 8 0.00012 | 832 | 0 (0.00000) | 687 (1.00000) | 34 (0.04949) | (0.867) 1dice2WmR 16 0.00024 | 1119 | 0 (0.00000) | 910 (1.00000) | 26 (0.02857) | (0.836) 1dice2xkj 32 0.00049 | 2842 | 1 (0.00038) | 2647 (0.99962) | 11 (0.00415) | (0.936) 1dice2zdo 64 0.00098 | 4053 | 5 (0.00130) | 3850 (0.99870) | 15 (0.00389) | (0.955) 1dice37Ee 128 0.00195 | 5460 | 11 (0.00209) | 5240 (0.99791) | 25 (0.00476) | (0.966) 1dice3jkp 256 0.00391 | 4080 | 17 (0.00437) | 3869 (0.99563) | 11 (0.00283) | (0.955) 1dice4J1m 512 0.00781 | 4903 | 29 (0.00615) | 4685 (0.99385) | 5 (0.00106) | (0.962) 1dice5wwE 1000 0.01526 | 5496 | 70 (0.01335) | 5172 (0.98665) | 1 (0.00019) | (0.954) 1dice61SN 1500 0.02289 | 4677 | 94 (0.02126) | 4327 (0.97874) | 5 (0.00113) | (0.946) 1dice6DPt 2000 0.03052 | 4966 | 149 (0.03162) | 4563 (0.96838) | 3 (0.00064) | (0.949) 1dice6gJg 3000 0.04578 | 5063 | 239 (0.04973) | 4567 (0.95027) | 5 (0.00104) | (0.950) 1dice6GV5 4000 0.06104 | 4916 | 291 (0.06243) | 4370 (0.93757) | 3 (0.00064) | (0.949) 1dice6wBx 6000 0.09155 | 7813 | 699 (0.09334) | 6790 (0.90666) | 3 (0.00040) | (0.959) 1dice6YgE 8000 0.12207 | 6873 | 800 (0.12094) | 5815 (0.87906) | 0 (0.00000) | (0.962) 1dice7EYz 12000 0.18311 | 13042 | 2369 (0.18949) | 10133 (0.81051) | 3 (0.00024) | (0.959) 1dice7fUk 16000 0.24414 | 29846 | 7154 (0.24374) | 22197 (0.75626) | 4 (0.00014) | (0.984) 1dice7W2A 24000 0.36621 | 16400 | 5925 (0.37234) | 9988 (0.62766) | 23 (0.00145) | (0.972) 1dice8EMZ 32000 0.48828 | 250677 | 121619 (0.48692) | 128151 (0.51308) | 111 (0.00044) | (0.997) 1dice97EC 32768 0.50000 | 98548 | 48494 (0.50024) | 48447 (0.49976) | 47 (0.00048) | (0.984) 1dice9wcM 48000 0.73242 | 59464 | 43278 (0.73446) | 15647 (0.26554) | 24 (0.00041) | (0.991) 1dice9wVt 64000 0.97656 | 5614 | 4318 (0.97472) | 112 (0.02528) | 757 (0.17088) | (0.924) ---------------------------------------------------------------------------------------------------------------------- | 543412 |
---------------------------------------------------------------------------------------------------------------------- Total Bets Made: 543412 Cumulative Wagers: 195424.98368132 BTC Cumulative Rewards: 193333.06261702 BTC Cumulative Fees Paid: 269.38745000 BTC Cumulative Unreturned: 2038.08327919 BTC ---- SD Profit/Loss From Games: 2091.92106430 BTC SD Profit/Loss With Fees: 1822.53361430 BTC Since Satoshi Dice started, there have been: Blockchain Tx: 1509892 : SatoshiDice Tx: 1010485 (66.9%) Blockchain MB: 641.5 : SatoshiDice Tx: 409.8 (63.9%)
|
|
|
The maximum bet depends on the funds available in the house wallet. It goes up when they've been winning. I can only assume that they've been losing recently. As of June 11th they were 700 BTC down.
|
|
|
House edge is about to be temporarily raised to 3% from 1.5%.
For how long and what purpose? When I saw that message I thought "they must be losing a lot and need to recover some of their losses" and went to track down etotheipi's thread where he posts statistics about satoshidice and how much they are up or down. I found it here: https://bitcointalk.org/?topic=80312 but it hasn't been updated since 11th June (at which point the house was down 700 BTC). Then I downloaded the script that he uses to generate that report with a view to making an up-to-date report, but I couldn't get it to run.
|
|
|
From the thread that Gox linked to: 2. Who’s affected by this problem?
People using Dwolla for their withdrawals, along with 5% of US Dollar wire transfers which is an unfortunate flow-on effect.
Could it be that you're seeing that "5% flow-on effect" that they refer to? I don't understand what that means, or why problems with Dwolla would affect unrelated US Dollar wire transfers.
|
|
|
Intersango fees are too high... I'm afraid I must leave you for greener pastures (after being with you since the britcoin switch). I will look into btc-e.com and bitfloor.com (0.1% and -0.1%/0.3% vs 0.35%/0.65%).
It looks to me like neither of these have a GBP market. According to http://bitcoincharts.com/markets/ only Gox and Intersango have GBP markets. Is that right?
|
|
|
If it was double, I could halve it. But it seems to be kind of random. Notice how the same 15 minute period shows two quite different volumes before and after I reloaded.
|
|
|
I reloaded the page, and the volumes changed, but are still wrong. 18k and 50k now: ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FjlmPs.png&t=663&c=LPkpaqj5fUjbAA)
|
|
|
How can that be?
Oh, I also notice that the daily volume at the top of the charts says 57k. The single large bar in the lower image is higher than the daily volume...
|
|
|
Look at these 2 screenshots, showing the same period of time. The first is a 5 minute view, the 2nd is a 15 minute view. The first shows only 18k of trades at 15:40, with very little either side of it, but the 2nd shows 89k of trades at the same time (the orange crosshairs are over the point I'm talking about in both images). How can that be? ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FdSUh8.png&t=663&c=Wbm7Y40q3jjqcQ)
|
|
|
Received Time (2012-05-11 12:18:15) 1CMKwkqWVD6BiuHWtrBFTiiCSuSxyyN677 (4,749 BTC - Output) (2012-05-09 22:59:22) 1KsssDbhj8sW5rvcQ6NHiNoxU2wmSVUrQT (3,750 BTC - Output) (2012-05-09 22:59:22) 1Fs1ixzNdPDqLcvsNieUtxd6nX5mZ67SR3 (3,199.9375078 BTC - Output) (2012-05-09 22:59:22) 1PqfGjpgZpdd4gbbGUsUWPJkVaVqoSLizY (3,519 BTC - Output) (2012-05-09 22:59:22)
These look like change outputs after 4 separate withdrawals of 250 BTC from the hot wallet. It could be they split large amounts up into smaller amounts to save on fees, or perhaps they transferred coins to the cold wallet in pieces of 250 BTC. Maybe they deposited to MtGox in 250 BTC pieces. Either way, each of those 4 amounts is the change from sending 250 BTC elsewhere, not a deposit to the hot wallet.
|
|
|
I just bought some bitcoins using Intersango.
I used Internet banking to transfer GBP to their bank account at 19:27 Monday evening British time, and got an email 20:35 the same evening to tell me the money was in my Intersango account.
It always surprises me how quickly the bank transfer works.
It took about 30 hours for my order to get filled, and the withdrawal took 5 seconds.
All in all a great service. If I hadn't bothered waiting to get a better price, the whole process would have taken less than an hour and a half from bank account to bitcoin wallet.
I paid 0.35% fees, which seems reasonable to me. I didn't try the other services a previous poster mentioned, but would be surprised if they can match the end-to-end speed of Intersango.
|
|
|
Hi, I have a huge problem with my bitcoind bitcoin server. It always crashes (about 2times a day) and I cant figure out what is wrong.. I`m not that into server administration, so I`m not able to fix this by myself. It runs on ubuntu lucid platform. I would appreciate your help. Thanks in advance. ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Do you manage the server yourself, or do you rent it from a company? I had a problem with bitcoind shutting down most days, and it turned out the shared hosting provider it was running on were doing some kind of backup most nights, which involved sending a signal to all running processes, which killed the bitcoind. It took dozens of emails back and forth before the hosting provider would even acknowledge that they were sending signals to all running processes - the support staff you get to talk to aren't always particularly knowledgeable.
|
|
|
Your backed up wallet has 100 "pre-made" addresses that it hadn't used yet. When you made your 10 new addresses after backing up, you got the first 10 of those pre-made addresses, and you'll get the same after restoring the wallet.
If you made transactions since backing up, the change may have gone to one of the addresses which you got as a 'new' address from before the crash, so that can get a little confusing - what used to be a 'new' address may now be a 'change' address, and vice versa. But you shouldn't lose any coins because of it.
|
|
|
The rootkit would make that file appear to be normal; that's what they do.
If you can boot from a known-good live CD then you'll be able to mount your root partition and see how that file really looks, before the rootkit has a chance to run and start masking itself.
|
|
|
Yea, I hear you, my 4BTC is peanuts compared to yours. ![Undecided](https://bitcointalk.org/Smileys/default/undecided.gif) But you did mention having backups so hopefully you'll get it resolved. I never backed mine up although I'm starting to realize that moving forward I should definitely back up my wallet weekly or be super paranoid and back it up a couple times a week even though I do an extremely low volume of transactions. Or, run 'bitcoin-qt -keypool=9999', wait for it to generate 9999 pool addresses, then back up the wallet, and you don't need to make another backup until you've used those 9999 addresses. "Using" an address happens each time you make a transaction which generates change back to yourself, and each time you click 'new address' in the 'receive coins' tab. Some RPC calls will also use a pool address, but if you don't use RPC you don't need to worry about that. 9999 can be any sufficiently large number, of course. By default it's only 100, meaning you need to back up at least every 100 spends you make.
|
|
|
|