I just noticed you have a twitter account. It says: Satoshi Dice @SatoshiDICE The Original SatoshiDICE.com - Win up to 65,000x your Bitcoin bet instantly. Fair, open, verifiable rolls. Over 99% breakeven odds. Which is inaccurate in a couple of ways.
|
|
|
You're right. It seems counter-intuitive to me that flipping three heads in a row (a 1-in-8 shot) takes an expected 14 flips to happen, but it does.
Because the average length of a round which ends when we either flip a tail or get 3 heads:
T : half the time HT : 1/4 the time HHT : 1/8 the time HHH : 1/8 the time
is 1*1/2 + 2*1/4 + 3*1/8 + 3*1/8 = 1.75 tosses - so the expectation is that it takes 1.75*8 = 14 flips.
Thanks for persevering with me!
|
|
|
For instance, I deposit 500 BTC, each week he gets 5BTC (1% of deposited funds.). He makes roughly 1.4285%~ on all interest that is accrued. (500BTC deposit. 35 interest total. .5 goes to pay.bc. .5/35.)
Where are you getting 5 BTC from? OK, it's 1% of 500 BTC - but where does the 1% come from?
|
|
|
Kind of ugly still, but better than what you're doing: $ bitcoind walletpassphrase '' 1 # not encrypted error: {"code":-15,"message":"Error: running with an unencrypted wallet, but walletpassphrase was called."} $ bitcoind walletpassphrase '' 1 # encrypted and locked error: {"code":-1,"message":"walletpassphrase <passphrase> <timeout>\nStores the wallet decryption key in memory for <timeout> seconds."} $ bitcoind walletpassphrase '' 1 # encrypted an unlocked error: {"code":-17,"message":"Error: Wallet is already unlocked."}
|
|
|
What if you only have one customer. He deposits 1 BTC and shorts at 10x leverage. Then the price of Bitcoin drops by a factor of 10 and he closes his position.
His balance is now 100 BTC. Where do you get the coins from to pay him?
|
|
|
There is a mean of 2 flips per game, so we'd expect exactly 10 heads in a row once every 2048 flips.
Is that 'exactly' where we are differing? The guy didn't have exactly 75 losses and then a win. He had 75 losses and quit playing. Who knows how many losses he would have had if he had kept playing. I think we expect at least 10 heads in a row once every 1024 flips. (exactly 11 heads is half as likely as exactly 10, exactly 12 is half as likely again,etc. 1/2 + 1/4 + ... = 1. ie. the chance of seeing exactly 10 is the same as the chance of seeing 11 or more. I see exactly 10 once every 2048 flips, I see 11 or more once every 2048 flips too. Combining these 2, I see 10 or more every 1024 flips.
|
|
|
Still trying to figure out why someone would dump coins like that?
Maybe they've been running a ponzi scheme and for some reason need to cash out quickly.
|
|
|
Watch me prove you wrong...we're going lower than $7.6
How about this? Let's say Halloween (October 31st). I'll buy 50 BTC at $5.50 each on that day from you. Deal? Chicken? Troll? Chicken Troll? ![Grin](https://bitcointalk.org/Smileys/default/grin.gif)
|
|
|
Here's the simulation code: #!/usr/bin/python
import random
trials = 100000 target = 10 max = 2**target * target
count = for trial in range(trials): in_a_row = 0 for flip in range(max): if random.random() < 0.5: in_a_row += 1 if in_a_row == target: count[flip] += 1 break else: in_a_row = 0
cumulative = 0 for flip in range(max): cumulative += count[flip] if count[flip]: print("%4d on flip %d; cumulative %6.2f%%" % (count[flip], flip+1, 100.00 * cumulative / trials))
|
|
|
quick bump. Satoshidice dice has a new max bet of 250 btc ![Shocked](https://bitcointalk.org/Smileys/default/shocked.gif) Site stability has been improved dramatically. They have 3 new bets, too: under 52000, under 56000, and under 60000.
|
|
|
Quick comment: It's even unluckier than that, since it's 1 chance in 17399 of a run of 75 or less bets in a row not winning - so that's going to have required 17399 * 75 = 1304925 or more bets to make it likely to have occurred once.
Enjoying you analysis so far - thanks for your work.
I'm not sure, but I don't think you should multiply by 75. Maybe add (75-1). Consider flipping a fair coin. How many times do you need to flip before it is 'likely' to get 10 heads in a row? It's a 1-in-1024 chance, so I would say you need to flip 1024 + (10-1) = 1033 coins to have a reasonable chance of 310 heads in a row. By your (implied) logic would you say you need 1024*10 = 10240 flips to make it likely? I just ran a simulation. Flipping coins until getting 10 in a row, and counting how many flips it took. I tried it 100,000 times. 116 (0.12%) of those times the first 10 coins were all heads. To have a 1% chance of getting 10 heads in a row I had to flip 29 times. For 10% I had to flip 221 coins, etc. Flipping 1033 coins gives a 39.71% chance of getting 10 heads in a row. But flipping 10239 coins gives a huge 99.34% chance. I have a feeling this is a binomial distribution thing, so I should be able to work out the maths rather than doing it by simulation. But I think that after 17399 * 75 plays you're almost guaranteed to have a losing streak of 75 or more. Oh, and the analysis I'm posting is based on work done by etotheipi - the OP in this thread. But I'm glad you appreciate it.
|
|
|
3 new games have been introduced: lessthan 52k, 56k, and 60k: Results: 2012-Jul-19 04:14pm (up to block 189848)
Address Target Should Win | #Bets | Win | Lose | Refunds | BTC In | BTC Out | Refund | Profit | RTP -------------------------------------------------------------------------------------------------------------------------------------------- 1dice1e6p 1 0.00002 | 10095 | 0 (0.00000) | 9826 | 269 | 49.71 | 0.01 | 16.20 | 49.70 | 0.039 1dice1Qf4 2 0.00003 | 984 | 0 (0.00000) | 915 | 69 | 7.78 | 0.00 | 5.38 | 7.78 | 0.023 1dice2pxm 4 0.00006 | 1493 | 0 (0.00000) | 1461 | 32 | 13.09 | 0.00 | 1.22 | 13.08 | 0.043 1dice2vQo 8 0.00012 | 1279 | 0 (0.00000) | 1240 | 39 | 17.68 | 0.00 | 3.65 | 17.67 | 0.027 1dice2WmR 16 0.00024 | 1470 | 0 (0.00000) | 1440 | 30 | 22.89 | 0.01 | 6.60 | 22.87 | 0.074 1dice2xkj 32 0.00049 | 3389 | 1 (0.00030) | 3377 | 11 | 105.91 | 100.40 | 1.29 | 5.50 | 94.798 1dice2zdo 64 0.00098 | 5162 | 7 (0.00136) | 5138 | 17 | 206.73 | 121.68 | 55.64 | 85.04 | 58.863 1dice37Ee 128 0.00195 | 6247 | 14 (0.00226) | 6185 | 48 | 1233.06 | 1143.24 | 40.25 | 89.81 | 92.716 1dice3jkp 256 0.00391 | 4562 | 21 (0.00462) | 4528 | 13 | 490.07 | 332.02 | 13.11 | 158.04 | 67.750 1dice4J1m 512 0.00781 | 6775 | 42 (0.00620) | 6728 | 5 | 1456.03 | 580.09 | 9.35 | 875.93 | 39.841 1dice5wwE 1000 0.01526 | 10486 | 150 (0.01431) | 10334 | 2 | 2051.62 | 1587.69 | 1.80 | 463.92 | 77.388 1dice61SN 1500 0.02289 | 6898 | 160 (0.02322) | 6732 | 6 | 2902.66 | 3248.48 | 15.00 | -345.82 | 111.914 1dice6DPt 2000 0.03052 | 7521 | 243 (0.03232) | 7275 | 3 | 3202.11 | 2904.42 | 9.24 | 297.69 | 90.703 1dice6gJg 3000 0.04578 | 6914 | 348 (0.05038) | 6559 | 7 | 4767.11 | 6317.21 | 24.99 | -1550.09 | 132.516 1dice6GV5 4000 0.06104 | 7399 | 473 (0.06395) | 6923 | 3 | 2699.06 | 2458.54 | 31.20 | 240.52 | 91.089 1dice6wBx 6000 0.09155 | 14175 | 1327 (0.09365) | 12843 | 5 | 8502.09 | 8668.21 | 7.01 | -166.12 | 101.954 1dice6YgE 8000 0.12207 | 28522 | 3556 (0.12471) | 24959 | 7 | 6058.32 | 5341.87 | 0.00 | 716.44 | 88.174 1dice7EYz 12000 0.18311 | 16117 | 3051 (0.18936) | 13061 | 5 | 6638.82 | 6772.67 | 14.50 | -133.85 | 102.016 1dice7fUk 16000 0.24414 | 42142 | 10219 (0.24253) | 31916 | 7 | 13161.09 | 12747.59 | 97.79 | 413.49 | 96.858 1dice7W2A 24000 0.36621 | 31588 | 11696 (0.37064) | 19860 | 32 | 13225.56 | 13222.07 | 212.63 | 3.49 | 99.974 1dice8EMZ 32000 0.48828 | 301258 | 146729 (0.48726) | 154400 | 129 | 92456.79 | 93222.19 | 2173.21 | -765.39 | 100.828 1dice97EC 32768 0.50000 | 126199 | 62916 (0.49885) | 63207 | 76 | 45118.62 | 43391.34 | 789.20 | 1727.28 | 96.172 1dice9wcM 48000 0.73242 | 88026 | 64754 (0.73600) | 23227 | 45 | 62057.75 | 60478.44 | 467.98 | 1579.30 | 97.455 1dicec9k7 52000 0.79346 | 23 | 18 (0.78261) | 5 | 0 | 10.68 | 11.64 | 0.00 | -0.96 | 109.002 1dicegEAr 56000 0.85449 | 11 | 7 (0.63636) | 4 | 0 | 0.32 | 0.27 | 0.00 | 0.04 | 85.085 1diceDCd2 60000 0.91553 | 4 | 3 (0.75000) | 1 | 0 | 2.55 | 2.71 | 0.00 | -0.16 | 106.514 1dice9wVt 64000 0.97656 | 5794 | 5545 (0.97847) | 122 | 127 | 5012.36 | 4819.54 | 239.20 | 192.81 | 96.153 -------------------------------------------------------------------------------------------------------------------------------------------- | 734533 | 311280 | 422266 | 987 | 271470.56 | 267472.47 | 4236.53 | 3998.08 | 98.527 --------------------------------------------------------------------------------------------------------------------------------------------
SD Profit before fees: 3998.08798832 BTC (1.473%) Cumulative Fees Paid: 369.74470000 BTC SD Profit after fees: 3628.34328832 BTC (1.337%) ---- Since Satoshi Dice started, there have been: Blockchain Tx: 2218777 : SatoshiDice Tx: 1359223 (61.3%) Blockchain MB: 939.4 : SatoshiDice Tx: 557.9 (59.4%) ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FmnygV.png&t=663&c=T23s8VcPVFjBOQ)
|
|
|
Now you are currently making 1% on all interest,
Learn to math Maybe he was referring to how payb.tc keeps 0.1% of the 7% interest. 0.1 is 1.43% of 7.0 ie. payb.tc keeps 1.43% of the interest. That doesn't make sense though... his statement was 1% on all interest. payb.tc keeps 1.43% of all the interest his members earn. Doesn't he? Maybe it's just a language issue. I would say "keeping 1% of all interest" rather than "making 1% on all interest".
|
|
|
I don't like how one bar's 'close' is often different than the following bar's 'open'. It looks like the value used for 'open' and 'close' are the first and last trades in that bar, whereas traditionally the 'open' price would be the last trade in the previous bar.
|
|
|
Now you are currently making 1% on all interest,
Learn to math Maybe he was referring to how payb.tc keeps 0.1% of the 7% interest. 0.1 is 1.43% of 7.0 ie. payb.tc keeps 1.43% of the interest.
|
|
|
I'm now running it in gdb to hopefully get a stack trace for you, though in my experience running it in gdb is often enough to stop the crash from happening.
I finally got a crash from the version I built with debugging symbols. Here's the backtrace: Let's look at all the bets ever placed at SatoshiDice.com there are 27 bet types lessthan 64000 is listed first SD Tx is in block 176627
Program received signal SIGSEGV, Segmentation fault. 0xb735eb18 in BtcUtils::readVarInt (strmPtr=0x4 <Address 0x4 out of bounds>, lenOutPtr=0xbffff1bc) at BtcUtils.h:243 243 uint8_t firstByte = strmPtr[0]; (gdb) where #0 0xb735eb18 in BtcUtils::readVarInt (strmPtr=0x4 <Address 0x4 out of bounds>, lenOutPtr=0xbffff1bc) at BtcUtils.h:243 #1 0xb735e446 in BinaryRefReader::get_var_int (this=0xbffff1e8, nRead=0x0) at BinaryData.cpp:203 #2 0xb736afd0 in BtcUtils::TxCalcLength (ptr=0x0, offsetsIn=0xbffff31c, offsetsOut=0xbffff328) at BtcUtils.h:564 #3 0xb736683d in Tx::unserialize (this=0xbffff2f8, ptr=0x0) at BlockObj.cpp:529 #4 0xb736bc24 in Tx::Tx (this=0xbffff2f8, ptr=0x0) at BlockObj.h:348 #5 0xb7367a58 in TxRef::getTxCopy (this=0x20b092b4) at BlockObj.cpp:718 #6 0xb74f0944 in _wrap_TxRef_getTxCopy (args=0xb7b4f34c) at CppBlockUtils_wrap.cxx:33750 #7 0x080f77c3 in PyEval_EvalFrameEx () #8 0x080f7e20 in PyEval_EvalFrameEx () #9 0x080fd804 in PyEval_EvalCodeEx () #10 0x080fe177 in PyEval_EvalCode () #11 0x0811acd0 in ?? () #12 0x0811b8e9 in PyRun_FileExFlags () #13 0x0811c4cc in PyRun_SimpleFileExFlags () #14 0x0812c7c6 in Py_Main () #15 0x0805da0b in main () (gdb) I'll leave the gdb session running, so if there are any commands you want me to type at it, I can do so. strmPtr=0x4 doesn't look good though. Pointers usually have high values, not 4...
|
|
|
Uhm... he might be manipulating a lot of things. He it not about to get burnt though.
I he continue to trade against the market, he will. The point is that he's not going to get burnt because it's not his coins he's playing with. I cant believe you even bothered to spell that out... waspoza seemed to be missing the point.
|
|
|
Apologies for the downtime. It's something to do with Bitcoind, every morning I wake up and it's consuming 8GB RAM and 100% CPU.
My solution: create a script which kills and restarts it periodically ![Cheesy](https://bitcointalk.org/Smileys/default/cheesy.gif) It probably takes a long time to restart, breaking things while it's down.
|
|
|
I'm not clear - does smoothie have the option to buy at $11 at the end of October, or the obligation to do so? i.e. can he elect to just pay the 25% and not take the coins without breaking terms of the contract?
Nope. I gotta buy 50 btc at $11 each. So why would you do that? Why not just buy them for $9 each right now and save yourself $100? I think the point of buying futures is that you're buying an option to trade at a certain price in the future, but are not obliged to do so.
|
|
|
Is it possible to point it to an other dir then ~/.bitcoin ?
Tried it some other way.
I have a specific problem. I had a blk0001.dat already when I first started the bitcoin-client. Instead of using that file it made a blk0002.dat and recently it made a blk0003.dat. The parser won't open the blockchain file: "Invalid argument: failed to open block chain file /home/jouke/.bitcoin/blk0001.dat"
I guessed that 0002 was actually 0001 and tried to symlink 0002 to 0001 and 0003 to 0002 in a separate directory, but your parser still won't open the file.
Any sugestions?
Temporarily set HOME to wherever you want it to read the blockchain from: $ HOME=/path/to/folder ./parser closure [...] fatal: No such file or directory: failed to open block chain file /path/to/folder/.bitcoin/blk0001.dat I doubt the parser made any blockchain files. It opens the files readonly, which won't create any files. About a week ago the blockchain file grew bigger than 2GB and so a 2nd file was created by bitcoin-qt: $ ls -l blk* -rw------- 1 chris chris 2097307549 2012-07-12 20:07 blk0001.dat -rw------- 1 chris chris 104659251 2012-07-19 02:52 blk0002.dat -rw------- 1 chris chris 751022080 2012-07-19 02:52 blkindex.dat I don't know where the 0003 file came from though!
|
|
|
|