If you can reliably reproduce it, next time you run it in gdb, can you put a breakpoint at FileDataPtr.h:290? If it crashes there, [...] I don't follow you. Putting a breakpoint there won't change where it crashes. Do you mean "if the breakpoint is triggered, [...]"? I guess that's what you mean. I'll watch out for it being triggered. I just noticed that editing FileDataPtr.h doesn't cause BlockUtils.o or ../_CppBlockUtils.so to be rebuilt, but it should. How did you generate the Makefile? It seems you're missing some dependencies. diff --git a/cppForSwig/Makefile b/cppForSwig/Makefile
-BlockUtils.o: BlockUtils.h BinaryData.h UniversalTimer.h BlockUtils.cpp
+BlockUtils.o: BlockUtils.h BinaryData.h UniversalTimer.h BlockUtils.cpp FileDataPtr.h
|
|
|
|
wow I would love to get in as much money as possible as a guaranteed win. Who is the single most trusted Escrow for such a large amount of BTC? I can't imagine one I would trust other than putting the wallet.dat file on an HD in my Aria box. The existing bet is for 5000 BTC, and is being escrowed by nanotube, the guy who set up the bitcoin-otc web of trust stuff. Here's the contract that both parties signed: https://bitcointalk.org/index.php?topic=91661.msg1013612#msg1013612and here's a very odd message from Pirate hinting a something happening in August that will decide the result of the bet and attempting to get Vandroiy to concede the bet: https://bitcointalk.org/index.php?topic=95008.msg1051580#msg1051580If you're serious about wanting some of that action, Pirate can be found in the #btcst channel on the Freenode IRC network. Or 'pirateat40' on these forums. I don't know whether he's looking to make more bets or not. 3) Donkdown is my poker forum and podcast, anyone can call me up any show and debate me on any topic. this invitation is open to you. We can debate my poker ability, results, and respect in the poker community. Listen to my last 2 podcast, where Jennifer Harmon was our special guest one week [...]
I actually listened to that show. I tuned in to get the Seals with Clubs freeroll password ("it grows back fast") and ended up listening to the whole show (and found out that what grows back fast is the hair on some poker player's ex-girlfriend's ass). So I can't say the show didn't have a certain educational value. The Jennifer Harmon interview was quite special. I liked how you coincidentally had her dogs on the show shortly before her because the guy you interviewed before her just happened to be looking after her dogs at the time! |
|
|
|
Okay, I re-read the contract now, apparently I misread 2013 as 2012 the last time. You have a point.
All I'm saying is, if it's that important, there are other options to explore than Occam's razoring the forums.
I don't think the bet proved anything. If pirate defaults, he will be up hundreds of thousands of bitcoins. He won't mind having lost a 5k bet; it will have been worth it for the good PR it generated - the "hey, BS&T must be legit if pirate is willing to bet such a large amount that he doesn't default" PR. Micon should get in on some of that action. Offer to make another 5k BTC (or 12k? that has a nice ring to it) bet with pirate on the same terms as the other bet maybe. It's a dead cert, right? |
|
|
|
If the Investment is returning poorly ,Can Pirate lower the interest rates to say 3-5% weekly and still win this bet ? or would that be a automatic win for vandroiy if it doesnt stay at 6.9 or 7% until october?
Pirate can change the interest rates so long as he gives notice, and doesn't reduce them to below 0%. This is a quote from the contract both parties signed: ===Change in BTCST ToS===
BTCST has the right to change the terms of its outstanding deposits at any time, as long as there is advance notice of at least 30 calendar days. Such changes may include changes in promised interest rates (as long as interest rates do not go below zero), changes in interest disbursement frequency (not to exceed 1 month intervals), interest tiers, forced withdrawals. Such changes shall not be construed to be a default event.
The event of dissolution of the BTCST business and return of all owed funds to all account holders, also shall not be construed as a default event.
|
|
|
|
Also we now have a lobby chat so please fell free to talk to anyone in the lobby, and a representative for PM Poker will be there as often as possible.
I tried that. It seems like the site is dead. I hung around in the lobby for half an hour and other than me not a single person spoke. |
|
|
|
|
I just tried logging in with just the first 31 characters of my password, then the first 30, etc.
It didn't help.
|
|
|
|
|
I just signed up, then closed the program immediately, opened it again, and tried to log in. It told me my password was incorrect.
I tried clicking the "Need help with my user name or password?" link, but nothing happened.
I'm using WINE in Linux to run the program.
Do you have a maximum password length? The password I used is 32 characters long and contains both a dash and an underline ('-' and '_'). My username is 'dooglus'.
|
|
|
|
From the SatoshiDice thread: I hope we are not derailing satoshidice's thread here  for a table containing 65 numbers I would use FF not FFFF  I will pm dooglus and discuss further. Dooglus you are welcome to share anything technical I discuss with you in PM - I just dont want to spam the SD thread to much If you use FF instead of FFFF, you will get 256 different numbers, from 0 to 255. There's no fair way of mapping those to 65 different numbers. 256/65 = 3.938 so most numbers would come up 4-in-256 times, and some would come up 3-in-256 times. If you have 64 numbers then it's much easier - every number comes up 4-in-256 times, since 256/64 = 4. |
|
|
|
For some perspective, AFAIK someone got into a bet with pirate for 5000BTC, and it's almost guaranteed that he will lose.
Do you have a source for that almost guarantee? |
|
|
|
So the deadline for, uh, something passed last night at 5 PM CST.
Yup. I suppose I might as well tell you guys what that is. There's something called the "Vegas Bonus" going on this weekend. All account holders with over 5k BTC as of Wednesday at 6 PM CT qualify. Any amount you add between Wednesday at 6 PM CT and Sunday at same time will be given a 1% bonus. You can guess what my thoughts are on this, so I won't bother. I think Frankie was referring to this deadline: Vandroiy has the following (2) options to choose from: - Concede the wager to me (pirateat40) per the details below.
- Vandroiy: Signed document confirming the action to concede the wager.
- pirateat40: Signed document accepting Vandroiy’s action.
- pirateat40: Will donate the entire wager balance (10,000 BTC) to a charity of the forums choosing.
- Don’t concede the wager and chance the outcome of Aug 14th.
- pirateat40: Nothing changes and pirateat40’s winnings (5,000 BTC) go to the charity of the forums choosing.
Vandroiy has until Thursday at 5:00PM CST to make his decision. I don't see how that is connected to a 1% bonus for BS&T lenders, since Vandroiy isn't a lender. And I think he ended up selecting special secret option three (3): - Wait for BS&T to default and collect your winnings
|
|
|
|
Results: 2012-Jul-27 11:14am (up to block 191066)
Address Target Should Win | #Bets | Win | Lose | Refunds | BTC In | BTC Out | Refund | Profit | RTP
--------------------------------------------------------------------------------------------------------------------------------------------
1dice1e6p 1 0.00002 | 11180 | 0 (0.00000) | 10898 | 282 | 65.22 | 0.01 | 18.19 | 65.20 | 0.030
1dice1Qf4 2 0.00003 | 1066 | 0 (0.00000) | 996 | 70 | 13.75 | 0.00 | 5.58 | 13.75 | 0.013
1dice2pxm 4 0.00006 | 1546 | 0 (0.00000) | 1512 | 34 | 19.35 | 0.02 | 2.22 | 19.33 | 0.106
1dice2vQo 8 0.00012 | 1343 | 0 (0.00000) | 1303 | 40 | 31.48 | 0.05 | 4.15 | 31.43 | 0.177
1dice2WmR 16 0.00024 | 1601 | 0 (0.00000) | 1568 | 33 | 64.81 | 0.19 | 7.40 | 64.61 | 0.298
1dice2xkj 32 0.00049 | 3815 | 1 (0.00026) | 3803 | 11 | 256.94 | 100.98 | 1.29 | 155.96 | 39.302
1dice2zdo 64 0.00098 | 5519 | 7 (0.00127) | 5495 | 17 | 285.58 | 121.97 | 55.64 | 163.61 | 42.709
1dice37Ee 128 0.00195 | 6514 | 16 (0.00247) | 6450 | 48 | 1274.06 | 1173.35 | 40.25 | 100.71 | 92.095
1dice3jkp 256 0.00391 | 5379 | 26 (0.00485) | 5339 | 14 | 607.59 | 379.58 | 13.11 | 228.01 | 62.473
1dice4J1m 512 0.00781 | 8559 | 61 (0.00713) | 8493 | 5 | 1729.56 | 1087.30 | 9.35 | 642.25 | 62.866
1dice5wwE 1000 0.01526 | 15157 | 226 (0.01491) | 14928 | 3 | 2707.58 | 2387.17 | 1.80 | 320.41 | 88.166
1dice61SN 1500 0.02289 | 8589 | 204 (0.02377) | 8379 | 6 | 3233.39 | 3651.47 | 15.00 | -418.07 | 112.930
1dice6DPt 2000 0.03052 | 10824 | 341 (0.03151) | 10480 | 3 | 3611.14 | 3343.93 | 9.24 | 267.20 | 92.601
1dice6gJg 3000 0.04578 | 8595 | 417 (0.04856) | 8171 | 7 | 5183.89 | 6651.15 | 24.99 | -1467.25 | 128.304
1dice6GV5 4000 0.06104 | 9626 | 601 (0.06245) | 9022 | 3 | 3372.52 | 3137.21 | 31.20 | 235.30 | 93.023
1dice6wBx 6000 0.09155 | 16923 | 1597 (0.09441) | 15318 | 8 | 9037.51 | 9197.04 | 7.01 | -159.52 | 101.765
1dice6YgE 8000 0.12207 | 35667 | 4418 (0.12391) | 31236 | 13 | 6871.23 | 6116.17 | 0.00 | 755.05 | 89.011
1dice7EYz 12000 0.18311 | 16657 | 3165 (0.19008) | 13486 | 6 | 6878.43 | 7023.19 | 14.50 | -144.75 | 102.105
1dice7fUk 16000 0.24414 | 45085 | 10938 (0.24265) | 34139 | 8 | 15553.51 | 16245.60 | 347.79 | -692.08 | 104.450
1dice7W2A 24000 0.36621 | 33590 | 12412 (0.36987) | 21146 | 32 | 13825.33 | 13762.52 | 212.63 | 62.81 | 99.546
1dice8EMZ 32000 0.48828 | 320174 | 156004 (0.48745) | 164036 | 134 | 100874.43 | 101381.77 | 2173.21 | -507.34 | 100.503
1dice97EC 32768 0.50000 | 133947 | 66842 (0.49932) | 67025 | 80 | 52658.10 | 51088.57 | 789.20 | 1569.52 | 97.019
1dice9wcM 48000 0.73242 | 98791 | 72641 (0.73569) | 26098 | 52 | 88368.22 | 86876.33 | 467.98 | 1491.88 | 98.312
1dicec9k7 52000 0.79346 | 1325 | 1060 (0.80000) | 265 | 0 | 2993.36 | 3075.08 | 0.00 | -81.72 | 102.730
1dicegEAr 56000 0.85449 | 850 | 703 (0.82706) | 147 | 0 | 866.91 | 832.12 | 0.00 | 34.79 | 95.987
1diceDCd2 60000 0.91553 | 279 | 252 (0.91304) | 24 | 3 | 78.51 | 75.87 | 0.00 | 2.64 | 96.633
1dice9wVt 64000 0.97656 | 6020 | 5765 (0.97878) | 125 | 130 | 5128.39 | 4935.94 | 239.20 | 192.44 | 96.247
--------------------------------------------------------------------------------------------------------------------------------------------
| 808621 | 337697 | 469882 | 1042 | 325590.91 | 322644.68 | 4491.03 | 2946.22 | 99.095
--------------------------------------------------------------------------------------------------------------------------------------------
SD Profit before fees: 2946.22962098 BTC (0.905%)
Cumulative Fees Paid: 407.10480000 BTC
SD Profit after fees: 2539.12482098 BTC (0.780%)
----
Since Satoshi Dice started, there have been:
Blockchain Tx: 2467594 : SatoshiDice Tx: 1489900 (60.4%)
Blockchain MB: 1040.8 : SatoshiDice Tx: 612.7 (58.9%)  |
|
|
|
I just had another crash while running the satoshidice armory code. This time it happened much earlier on, while parsing the blockchain: Opening file 1: /home/chris/.bitcoin//blk0001.dat
Opening file 2: /home/chris/.bitcoin//blk0002.dat
Highest blkXXXX.dat file: 2
Attempting to read blockchain from file: /home/chris/.bitcoin//blk0001.dat
/home/chris/.bitcoin//blk0001.dat is 2000.15 MB
Attempting to read blockchain from file: /home/chris/.bitcoin//blk0002.dat
/home/chris/.bitcoin//blk0002.dat is 210.012 MB
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff54a9262 in CryptoPP::X86_SHA256_HashBlocks (state=0x7ffff585a830, data=0x0, len=256) at sha.cpp:435
435 );
(gdb) where
#0 0x00007ffff54a9262 in CryptoPP::X86_SHA256_HashBlocks (state=0x7ffff585a830, data=0x0, len=256) at sha.cpp:435
#1 0x00007ffff54aa2f4 in CryptoPP::SHA256::HashMultipleBlocks (this=<optimized out>, input=<optimized out>, length=258) at sha.cpp:453
#2 0x00007ffff5484cc7 in CryptoPP::IteratedHashBase<unsigned int, CryptoPP::HashTransformation>::Update (this=0x7ffff585a7c0, input=0x0, len=258)
at iterhash.cpp:55
#3 0x00007ffff53d150c in BtcUtils::getHash256(unsigned char const*, unsigned int) () from ../_CppBlockUtils.so
#4 0x00007ffff53cb1fa in TxRef::getThisHash() const () from ../_CppBlockUtils.so
#5 0x00007ffff53db4bf in BlockDataManager_FileRefs::insertTxRef(BinaryData const&, FileDataPtr&, BlockHeader*) () from ../_CppBlockUtils.so
#6 0x00007ffff53dc904 in BlockDataManager_FileRefs::parseNewBlockData(BinaryRefReader&, unsigned int, unsigned int, unsigned int) () from ../_CppBlockUtils.so
#7 0x00007ffff53e5296 in BlockDataManager_FileRefs::parseEntireBlockchain(std::string, unsigned int) () from ../_CppBlockUtils.so
#8 0x00007ffff54d4a7d in _wrap_BlockDataManager_FileRefs_parseEntireBlockchain () from ../_CppBlockUtils.so
#9 0x000000000042ecbc in PyEval_EvalFrameEx ()
#10 0x00000000004317f2 in PyEval_EvalCodeEx ()
#11 0x000000000042a998 in PyEval_EvalFrameEx ()
#12 0x00000000004317f2 in PyEval_EvalCodeEx ()
#13 0x000000000042a998 in PyEval_EvalFrameEx ()
#14 0x00000000004317f2 in PyEval_EvalCodeEx ()
#15 0x000000000054b171 in PyRun_FileExFlags ()
#16 0x000000000054b7d8 in PyRun_SimpleFileExFlags ()
#17 0x000000000054c5d6 in Py_Main ()
#18 0x00007ffff68e576d in __libc_start_main (main=0x41b900 <main>, argc=2, ubp_av=0x7fffffffe498, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>, stack_end=0x7fffffffe488) at libc-start.c:226
#19 0x000000000041b931 in _start ()
(gdb) |
|
|
|
There's a feature called the 'time weight'.
The weighing will help reduce the effect of people putting on large bets after the result is known, but such behaviour would still significantly harm the return on winning bets placed in advance, especially if the default happens significantly before the deadline of the bet. I would hope bets placed after the default became apparent would be cancelled, but I don't see anything about this on their site. How are the losing bets distributed?
Here is the breakdown of the distribution:
45% goes to the bet winners proportional to their bets.
45% goes to the bet winners proportional to their weighted bets.
5% goes to the user who submitted the bet.
5% goes to the site.
Here is an example:
Let's say total of 10 btc is lost on a statement and there are three users who won:
User A bets 1 btc 6000 minutes before the deadline (weighted bet of 6000), she is also the submitter.
User B bets 3 btc 1000 minutes before the deadline (weighted bet of 3000)
User C bets 1 btc at the last second (weighted bet of 0)
4.5 btc is distributed proportional to bets:
User A gets 0.9, User B gets 2.7, User C gets 0.9.
4.5 btc is distributed proportional to weighted bets:
User A gets 3.0, User B gets 1.5, User C gets 0.
User A also receives 0.5 commission as a submitter.
So in total:
User A profits 4.4, User B profits 4.2, User C profits 0.9, and site profits 0.5.
Obviously every winner also receives back the bet they put.
Take home message: Bet early, win more. |
|
|
|
Even with this updated code as fireduck pointed out some numbers have a slightly higher distribution (1 more than those that do not for every 65535). Which results in some numbers having a 0.02% edge over others.
Wouldn't the edge then be 1/65535 (or 1/65536, but it makes little difference for this calculation), which is 0.000015 or 0.0015%? |
|
|
|
$number = int(( (($number - 1) / 65535) * 38) + 1);
If I cannot resolve this satisfactorily I will build a new roulette table that has 65 numbers (FF).
You're still dividing by 65535. That's still wrong. And 65 doesn't divide into 65536 any better than 38 does. You need powers of 2. May I suggest 32. Or 64. |
|
|
|
There's a difference between hiding and ignoring  Yes, and both are suggested on the new bitcoinmax page. No, it was more ignore them and eventually they'll drop off during the course of normal discussion. Which is true. No-one here has the ability to hide posts. The suggestion was to: "make a few posts/replies about something else, so that the troll post is quickly pushed off the page" i.e. post in order to push their post off the page. |
|
|
|
There's a difference between hiding and ignoring Yes, and both are suggested on the new bitcoinmax page. |
|
|
|
It took me a while to find the FAQ. The big yellow underlined link-looking "PLEASE SEE THE FAQ" isn't actually a link. The "FAQ" link is hidden inside the roulette table itself. You're missing the 'bet 2', 'bet 3', 'bet 4', 'bet 6' bets. Usually it's possible to bet on groups of numbers like that. In the FAQ: Q> Are you on any bitcoin forums ?
A> No, I occasionally lurk on #bitcoin but I shall be signing up shortly to announce the public test.
The question isn't in bold like all the other questions, and the answer is incorrect. Q> How do you work out the senders address ?
Missing apostrophe in 'senders'. This took me many nights of starting at bitcoind
Staring? The 2 alternatives to my method is
Alternatives are. Not is. idex
index? |
|
|
|
$number = int(1+(($number / 65535) * 38));
if $number is 65535 then the result of the above is 39. 37 and 38 are 0 and 00. What's 39? You should divide by 65536, not 65535. Better would be a simple: $number = ($number % 38) + 1 You still have 1724/65536 chance of getting some numbers and 1725/65536 chance of getting others, but there's not much difference between the two. |
|
|
|
p.s. it would be great if everyone could give their opinion of the new page  I'm not sure I agree with it. It's quite possible that BS&T is a scam and will default one day. We all know that, hopefully have taken that possibility into account when deciding whether or not to get involved, and shouldn't feel threatened by others warning about that possibility. I agree that there has been enough argument about this already, and so it's a good idea not to engage in yet more fruitless discussion of "is it a scam or not", but attempting to hide dissenting comments from view doesn't seem right either. |
|
|
|
|
Show Posts
