Here's a counter question; when did bit-x pass independed financial audit ?
Here's another; what did you have for breakfast today? But can we please try to keep this on-topic? If bit-x have been asked for a proof of solvency and in response made a bunch of weak attempts to avoid the question, then that's a matter for their thread. It's nothing to do with the question at hand. I was making a point that just because you have someones adv. in signature, doesnt mean you are their shill account. And you can not judge someone just because they dont want to do what you ask them to. Its funny that most of people attacking dadice are competitor sites that are loosing customers to rival. Just an observation  What competition? They don't have any real gamblers. All their ~150M bets is dust of 1 to 100 satoshis from faucet. We are concerned because another scam will hurt whole community. Not because someone is afraid of competition. NLNilco or Quickseller don't have a casino, as well as several other members. Well yesterday we had one player losing 15 btc, 9 btc of those in one bet. On Sunday we paid out to 1 player 18+ btc and to another one 10 btc. Must I post the tx id's here to prove? Great to know that you call that dust. You should maybe in-between follow our HR section -- growing daily as well. Funny how you are willing to post trx ids of those members without even asking them, but deny to publish cold wallet or other statistics that each and every site publish to be transparent. |
|
|
|
Dear Friends, The Bitcoin secular downtrend has urged us to come up with a hedging solution to eliminate the adverse impact of highly volatile and depreciating value of bitcoin. For BitDice investors we contemplate to offer the capability of locking-in hard USD value of coin investments via instantaneous hedging of capital with financial instruments. Technically it implies the cooperation with one of the largest and most advanced crypto-currency trading platform BITFINEX ( www.bitfinex.com). To lock-in the value of bitcoin, investors will get the option to take offsetting position on the market, thus preserving the principal USD value of investment BitDice has been long using hedging techniques to secure its own BTC capital during the downfalls of bitcoin. We are experienced players on the capital market and capable to cater the similar service to our investors. Give us a shout if this additional service sounds interesting to you. Regards, Alex |
|
|
|
|
Alright. I should probably elaborate more.
Assume there is a predefined setup for generating a stream of bets with bet amount of 1 BTC but variable multiplier and High/Low selection of rolls (and no bias in terms of house edge). Each bet will produce result (profit or loss) that will be added to the previous result (again profit or loss). Now, with each bet in progress, you’ll get a cumulative time-series values of so-called betting performance that will look like a curve starting at zero on both X and Y axes. There is no way to know what form the curve will eventually take after N-number of bets is executed, thus the outcome is unpredictable.
Now as regards to the odds. As I mentioned, we may introduce multitude of different combinations for placing bets. For the sake of simplicity, consider a binary option to illustrate how it works: You bet on the curve that ends (1) positive or (2) negative - for the curve to end positive, profits should prevail over losses. Since the process is random, there are basically 50/50 chance of either outcome. So BitDice will take on first player bet with 2.00x payout for either case. As further players arrive to the game they will realize that the odds are no longer 50/50 for them, as the first player, who’s already bet for (1) option, will skew the multiplier payouts.
In this particular example, placing a first bet on (1) option for the bettor that follows him will somewhat decrease multiplier for (1) and increase multiplier for (2), bringing incentive for other players to bet on less crowded option (2). As result, every incoming player will affect payout stakes after committing his bet, where in fact the outcome WILL hold a theoretical distribution of odds, in this case 50/50.
|
|
|
|
|
Guys,
BitDice contemplates an idea to introduce a new betting concept on top of what it operates by far. There are certain technicalities we need to address first, however, we would like to share the basic idea with you in order to get your feedback. You are very welcome to let us know your thoughts if it is something that you’d like to see working and/or willing to participate in.
The concept revolves around an idea to create the environment where players or group of players are able to bet against each other on an outcome of a random event. The event, which we would like to bring forward, will be based on the same principle of rolling a dice but will undergo some additional mathematical manipulations.
To generate the event, BitDice will run a stream of bets according to a disclosed algorithm similar to the current. The results of each consecutive bet will be summed up and reflected on the chart in terms of a curve. Once the certain number of bets is generated and the curve is fully built, the event will produce an outcome with a final numerical values upon which bets will be checked.
There will be multiple combinations of outcome a player will choose from. The simplest, for instance, would be an outcome of two mutually exclusive events such as if the curve ends up in positive or negative territory.
Prior to generating a curve, players will be asked to place their bets with our model’s estimated odds. Odds will be a function of players’ preferences who already committed their bets and will change dynamically while bookmaking in progress. Initially, BitDice will facilitate a start-up liquidity for the purpose of making first bets going. However, there will be no intention for BitDice to take on any side in the game.
We believe the idea might be interesting from two perspectives. First, the game will be more exciting to play when opponents are human-being participants instead of a house. Second, odds will be never fixed and are basically exposed for bargain hunting opportunities depending on the current bets allocation. These two reasons alone shall bring BitDice a bit of fresh air of innovation.
Regards,
Alex
|
|
|
|
|
Hello guys
Today I've made some updates to the site, more to come.
* Fixed visual bug with wagered amounts and various stats on BlackJack
* Blackjack wagered amount now affects your level
* Blackjack wagered amount counts to rain
* Best bets for BJ
* More strict check on Autobot, should fix double betting with autobot for a very few users. [In case you have installed Madroller's bot you still can have this issue, Mad works on the fix.]
|
|
|
|
Sup fellas Transaction: a865a5e6dd5bceee5c597a98ab4ba64ff59c03a2df6a305877f75bf1ae7a802d |
|
|
|
I've often had the opposite experience. A few days ago I tried withdrawing 550 CLAM, which is worth about 2 BTC. The site told me I had to wait for the cold wallet. I thought the site actively staked all its CLAM, so why is it telling me I have to wait for a cold wallet transaction? It would be useful to know how much is available for withdrawal in the hot wallet. Currently I have to guess and hope that you will return my coins when I ask for them. Having to wait 8 hours for a relatively small withdrawal makes it not worth playing. I want to be able to withdraw quickly so I can continue staking my coins rather than having the staking rewards go to your site's investors. Coins are staking but on the separate server. Thus, hot wallet keeps about 10-15% of all invested amount. That's why you are waiting for processing. |
|
|
|
Hello, Another day, another nice bug for you You shouldn't change currency in the middle of the game I know about it. It's just visual, you have REDD not BTC This one and all issues with stats will be updated with next huge deploy. |
|
|
|
I can't chat as I lost my balance.. :/
Try again |
|
|
|
Reporting bug:
Under stats, player profit is shown as Negative (for positive player profit)
That is say, a profit of 1BTC is shown as -1BTC
Best regards
ndnhc
That's known issue, linked to stats, will be updated when stats will be merged, atm wagered amount on BJ doesn't count to receive rain. Uhm.. I was playing Blackjack. The server stopped responding and then the dealer started acting differently.. What's the deal?
Lost .02 BTC I had in play... :/
Come to chat, need your bet id to check. |
|
|
|
When I withdraw, it sends me 0.002 CLAM less than I ask for. I guess that's a fee, but it would be nice if it told me when I was withdrawing.
Also, it's 20 times bigger than the fee of 0.0001 CLAM that is actually included in the transaction.
Yeap it uses litcoins fee. I'm gonna add information and lower it. Thanks |
|
|
|
Alex fixed the "stand on soft 17" bug, but it's still not right:  Doog, this one is fixed too, can you check again? |
|
|
|
How does BitDice generate enough income to cover this? It looks like even all the BTC from your investment as well as commission on profits wouldn't even come close to covering it.
It seems to me the only important question is whether bitdice is still solvent. I expect they publish a weekly list of investor balances, and publish their cold wallet address, so it shouldn't be too hard to check. If they don't do this, investors should demand that they do. Nobody wants to invest in an insolvent dice site. We are solvent doog, coldwallet in the first post in this thread, it contains > 90% of the investor funds, and yeap, I should regularly post anonymous stats of the investor balances. I did it but not frequently enough. |
|
|
|
and it outputs this: bet_hash: 49dde939d58d494f4dbb3a510b86abe4f62d2c17a6a83bb3f5f9991a47cdac77b38008f8caf6938c6e491e6fd54ab020b1b961c787fd296cad4b2cae4ce540f6
["7C", "4D", "2S", "10S", "9C", ...]
Note that the 'bet hash' is the same as I see when I click the bet ID:  What am I doing wrong now? Maybe the Ruby code in the FAQ could be improved so that it will actually run and give the same shuffle as the game is using. I will check the soft 17 bug, with validation here's the correct code: require 'digest'
SECRET='7fc84a2d8dbf0d50b79bd771677354dd85b1b64129f6f54f7fb4def6973aba2598044eaa826a6020d41be7ec255e88b43c1b0afc2522c657aa6922b7852414d6'
USER_SEED='everymagicseed'
USER_ID='8798'
USER_BET_NUMBER='73'
deck = %w[AS 2S 3S 4S 5S 6S 7S 8S 9S 10S JS QS KS AH 2H 3H 4H 5H 6H 7H 8H 9H 10H JH QH KH AD 2D 3D 4D 5D 6D 7D 8D 9D 10D JD QD KD AC 2C 3C 4C 5C 6C 7C 8C 9C 10C JC QC KC AS 2S 3S 4S 5S 6S 7S 8S 9S 10S JS QS KS AH 2H 3H 4H 5H 6H 7H 8H 9H 10H JH QH KH AD 2D 3D 4D 5D 6D 7D 8D 9D 10D JD QD KD AC 2C 3C 4C 5C 6C 7C 8C 9C 10C JC QC KC AS 2S 3S 4S 5S 6S 7S 8S 9S 10S JS QS KS AH 2H 3H 4H 5H 6H 7H 8H 9H 10H JH QH KH AD 2D 3D 4D 5D 6D 7D 8D 9D 10D JD QD KD AC 2C 3C 4C 5C 6C 7C 8C 9C 10C JC QC KC AS 2S 3S 4S 5S 6S 7S 8S 9S 10S JS QS KS AH 2H 3H 4H 5H 6H 7H 8H 9H 10H JH QH KH AD 2D 3D 4D 5D 6D 7D 8D 9D 10D JD QD KD AC 2C 3C 4C 5C 6C 7C 8C 9C 10C JC QC KC AS 2S 3S 4S 5S 6S 7S 8S 9S 10S JS QS KS AH 2H 3H 4H 5H 6H 7H 8H 9H 10H JH QH KH AD 2D 3D 4D 5D 6D 7D 8D 9D 10D JD QD KD AC 2C 3C 4C 5C 6C 7C 8C 9C 10C JC QC KC AS 2S 3S 4S 5S 6S 7S 8S 9S 10S JS QS KS AH 2H 3H 4H 5H 6H 7H 8H 9H 10H JH QH KH AD 2D 3D 4D 5D 6D 7D 8D 9D 10D JD QD KD AC 2C 3C 4C 5C 6C 7C 8C 9C 10C JC QC KC AS 2S 3S 4S 5S 6S 7S 8S 9S 10S JS QS KS AH 2H 3H 4H 5H 6H 7H 8H 9H 10H JH QH KH AD 2D 3D 4D 5D 6D 7D 8D 9D 10D JD QD KD AC 2C 3C 4C 5C 6C 7C 8C 9C 10C JC QC KC AS 2S 3S 4S 5S 6S 7S 8S 9S 10S JS QS KS AH 2H 3H 4H 5H 6H 7H 8H 9H 10H JH QH KH AD 2D 3D 4D 5D 6D 7D 8D 9D 10D JD QD KD AC 2C 3C 4C 5C 6C 7C 8C 9C 10C JC QC KC]
bet_hash = Digest::SHA512.hexdigest (SECRET + ':' + USER_SEED + ':' + USER_ID + ':' + USER_BET_NUMBER)
random = Random.new(bet_hash.to_i(16))
deck.shuffle!(random: random)
p deck
What output do you see when you run that? I see the same shuffled deck as from my version of the code, and it doesn't correspond to the cards I saw. Here's the text version of the image I posted showing the actual cards that were dealt: Bet Amount 2.0 CLAM
Profit -2.000000 CLAM
Dealer Hand 3S,3D,AS (17)
Player Hand LOST: 9C,2S,4H (15)
Bet Number 73
User Seed everymagicseed
Bet Hash 49dde939d58d494f4dbb3a510b86abe4f62d2c17a6a83bb3f5f9991a47cdac77b38008f8caf6938c6e491e6fd54ab020b1b961c787fd296cad4b2cae4ce540f6
How does it get 3S,3D,AS from that shuffle? $ ruby bitdice2.rb
["7C", "4D", "2S", "10S", "9C", "8H", "AC", "5H", "3H", "6S", "9S", "8D", "5C", "7C", "3H", "9H", "QH", "2S", "8S", "9H", "KH", "4S", "9S", "8C", "KS", "5S", "7C", "4S", "QS", "QC", "10H", "JH", "JH", "KS", "7D", "7D", "6C", "QH", "4S", "4D", "7H", "KS", "AS", "3C", "2S", "AS", "QH", "8H", "7S", "3C", "5D", "2D", "5D", "JD", "QS", "JD", "QS", "9D", "9D", "2D", "JH", "2C", "9C", "2D", "7H", "6C", "8C", "7C", "8S", "JD", "7S", "9H", "3S", "8S", "7S", "4H", "7D", "8D", "6S", "KH", "AC", "QD", "KH", "QC", "3D", "3S", "8H", "3D", "3H", "4C", "QS", "QS", "6D", "9H", "8S", "JD", "AC", "3D", "JH", "4S", "5D", "2D", "AH", "7S", "3D", "6S", "5S", "5C", "QD", "8C", "5C", "KC", "6C", "4H", "AD", "KS", "5C", "7C", "5D", "7H", "AD", "JD", "2D", "4S", "6H", "3H", "2C", "6S", "QD", "6D", "QS", "AD", "5S", "3H", "AD", "6H", "9H", "8S", "3C", "2H", "2H", "6C", "5D", "7S", "2H", "QC", "4D", "9S", "6H", "7H", "JS", "6S", "8H", "KD", "6C", "6D", "7D", "10C", "10S", "QD", "9D", "2D", "QD", "2C", "4D", "10H", "9D", "3C", "AC", "KC", "KC", "8C", "JS", "QS", "6D", "9H", "JC", "3C", "KD", "7S", "JS", "10C", "8S", "5H", "6C", "6H", "5H", "2H", "2S", "4C", "9D", "2H", "3D", "JC", "JH", "AS", "AS", "9D", "5H", "KS", "KH", "3H", "AD", "8H", "8H", "3C", "10C", "5S", "10C", "3S", "6H", "5D", "AD", "5H", "9C", "4H", "KH", "4H", "10D", "2D", "JH", "3S", "10H", "7H", "10D", "AC", "JH", "6D", "QC", "6H", "10S", "4S", "4C", "AH", "10C", "4D", "10S", "JC", "10D", "5C", "8C", "KD", "AH", "KD", "4H", "10D", "KC", "AH", "KD", "8D", "7H", "8H", "10H", "AH", "6H", "QH", "4D", "9S", "5H", "10D", "9C", "8S", "2S", "3D", "10H", "JC", "8D", "QC", "7D", "JS", "JD", "7D", "JS", "7C", "4C", "6H", "9H", "4C", "8H", "KS", "8D", "QC", "2S", "4S", "10H", "8D", "QC", "4H", "JS", "8C", "10C", "5S", "AC", "6D", "9C", "10H", "3C", "9D", "5C", "2C", "6S", "5H", "JC", "AH", "9S", "KC", "AS", "9S", "5H", "5S", "AD", "10D", "6D", "AS", "KD", "5S", "6S", "3D", "4C", "AH", "8C", "5S", "AS", "10D", "9D", "10H", "JH", "4H", "7H", "7H", "JD", "5C", "JS", "6C", "AS", "QS", "10D", "9C", "KC", "5D", "9H", "2H", "4C", "QD", "AC", "2C", "9S", "7D", "2C", "2C", "9C", "2H", "2C", "5D", "QH", "JS", "3H", "3H", "9C", "KD", "10S", "AH", "4S", "KH", "QH", "QH", "10S", "QD", "10S", "KH", "KD", "6C", "KS", "JC", "4C", "4D", "4D", "2S", "2S", "4H", "QH", "3C", "7S", "3S", "3S", "KC", "JD", "6D", "KS", "JC", "QC", "8C", "2D", "7C", "3S", "5C", "KH", "QD", "7S", "AC", "7C", "8S", "10S", "AD", "8D", "7D", "2H", "8D", "3S", "10C", "6S", "KC", "JC", "9S", "10C", "3D"]
Wow, really strange, that's my output of the exact code, and it's the same as on server: ~ » ruby -v
ruby 2.1.5p273 (2014-11-13 revision 48405) [x86_64-darwin14.0]
~ » ruby v.rb
["9C", "3S", "2S", "3D", "4H", "AS", "AD", "8S", "JS", "JD", "QC", "4H", "AD", "6D", "9C", "3S", "9D", "QC", "6S", "AH", "JH", "QD", "4C", "9C", "8D", "5H", "3C", "2S", "KH", "5D", "KH", "9H", "7D", "7S", "10S", "10H", "KS", "2D", "AH", "9C", "5H", "5C", "2C", "5H", "3S", "5H", "9H", "7S", "7S", "6D", "QH", "3C", "JC", "2C", "10C", "9C", "2H", "6S", "9H", "3H", "AD", "QD", "4D", "9S", "2S", "3H", "6S", "5C", "QH", "9H", "4S", "JD", "4S", "2H", "7C", "10C", "8S", "5C", "10D", "QC", "7C", "JH", "10H", "KD", "JH", "6C", "6H", "KC", "6S", "QS", "KH", "9S", "AC", "AD", "6C", "KC", "JC", "QD", "7D", "7C", "JS", "KC", "8H", "2S", "4H", "8H", "AH", "KS", "AS", "JD", "10H", "7C", "4C", "JD", "2H", "7H", "10D", "7H", "9H", "2C", "7C", "JH", "QD", "7D", "KD", "KS", "4D", "QC", "2H", "AH", "8S", "AD", "3C", "8C", "10C", "9C", "AH", "4C", "6D", "3H", "AC", "10S", "KH", "7S", "2D", "3C", "2D", "2H", "5H", "AC", "7H", "3D", "QH", "8S", "8H", "7S", "7C", "6C", "JC", "10H", "KH", "6S", "QS", "5C", "5S", "4S", "10C", "2C", "6D", "6C", "JD", "6C", "AC", "KH", "10D", "8C", "2D", "AH", "4D", "JC", "5S", "JD", "9C", "6C", "8D", "6D", "3D", "9D", "4S", "6S", "4S", "7S", "KD", "3C", "8D", "KC", "10D", "7H", "4H", "KD", "6D", "8D", "5D", "5S", "6H", "KC", "10S", "QS", "JC", "4H", "2C", "3D", "7D", "4C", "3D", "KS", "8H", "5H", "JD", "8D", "7H", "8S", "AC", "JS", "4S", "2D", "3H", "AS", "3S", "9D", "10C", "6C", "9S", "9D", "9H", "10S", "6D", "4S", "KS", "9H", "4C", "JH", "6H", "AD", "2S", "AS", "JS", "6S", "3C", "10H", "AD", "5D", "AS", "2D", "10S", "4S", "5C", "7H", "5S", "8H", "JC", "2C", "9D", "4C", "6H", "8S", "10D", "AC", "QC", "10H", "KD", "QS", "10C", "5S", "10D", "3D", "7D", "QD", "3H", "10S", "5S", "QH", "5D", "5D", "9S", "AS", "QS", "10S", "8H", "4D", "JD", "8C", "AH", "AS", "3H", "JS", "5D", "4C", "3S", "4D", "2H", "7S", "KD", "6H", "QH", "9S", "5S", "KC", "2D", "6H", "AS", "5C", "QS", "3D", "2S", "JS", "9S", "QC", "AD", "8C", "KH", "QC", "4H", "6H", "5C", "QC", "6H", "3C", "7H", "9D", "2D", "8C", "9H", "5S", "JC", "KH", "10D", "7D", "AC", "4D", "7D", "8D", "JC", "3S", "4H", "8C", "JS", "3S", "2C", "7S", "QD", "QH", "3D", "2C", "QD", "4D", "AC", "3S", "2S", "5C", "JH", "5H", "9S", "5D", "3C", "JH", "10H", "4C", "QH", "10D", "2S", "8S", "10C", "KS", "8H", "7H", "3H", "8H", "5H", "KC", "8C", "JH", "8C", "6C", "6D", "QD", "10S", "2H", "3H", "10H", "KD", "AH", "2H", "8D", "4H", "9S", "KC", "9C", "KS", "8S", "JS", "KD", "8D", "9D", "QH", "10C", "7D", "QS", "QS", "7C", "9D", "KS", "5D", "6S", "4D", "7C"]
Can you tell me your ruby version? |
|
|
|
How does BitDice generate enough income to cover this? It looks like even all the BTC from your investment as well as commission on profits wouldn't even come close to covering it.
Stat's have been reset with the release of V3, I'm considering to merge them as it subject to question. But our profits was at 950BTC, and at some time I owned about 70% of the bankroll and that's only Bitcoin. |
|
|
|
Hello, I just want to know if you at Bitdice have any plans regarding adding faucet to your site? Every big dice site has one already... It would be nice feature. Also I want to know what is "keyboard betting"?
I'm not sure about faucet, we have a RainBot which funds active players, and at least once a week it rains like 1M redd or 200k doge at once.. However to receive those you need to play in the last 24 hours. Keyboards betting means you can play with shortcuts, pressing H or L on the keyboards. |
|
|
|
I'm sure you said it would never happen in the first place, but it did.
Just worth noting that people are entrusting you with over 1,000 BTC of their money. What happens when you can't cover it yourself?
Do you now any service which was not affected by any loss at all at any given time? We all make mistakes. First of all the loss is always limited to the amount in hot wallet, second I will cover any loss, BitDice generates much more profits than this loss. However everything is just speculation. The main point is - this will not ever happen again and I'm not gonna risk any investors funds. |
|
|
|
I mean the admin fucked up his test code and allowed someone to withdraw 1/10th of the bankroll without depositing or betting.
Yes I did and I paid for that. Also I've updated the code such even If I repeat it, this will not happen again, nor any other similar incidents. |
|
|
|
It happened again. Even though it says right on the table that the dealer hits soft 17: ... I bet 1 CLAM, was dealt 11 vs. dealer's 3, so I doubled, the dealer got soft 17, stood, and won! ... Such sadness.  I tried verifying this hand to see whether I would have won or not if the game wasn't buggy, but I couldn't get it to verify. First I tried using the Ruby code from the FAQ:  but it won't even run. It complains:
bitdice.rb:7:in `<main>': uninitialized constant Digest (NameError)
so it looks like the code isn't really complete. I don't know much Ruby at all, but I was able to get past that by adding:
require 'digest/sha1'
Then it complained:
bitdice.rb:13:in `<main>': undefined local variable or method `initial_deck' for main:Object (NameError)
so I added a definition for the initial deck. I finished up with this: SECRET='7fc84a2d8dbf0d50b79bd771677354dd85b1b64129f6f54f7fb4def6973aba2598044eaa826a6020d41be7ec255e88b43c1b0afc2522c657aa6922b7852414d6'
USER_SEED='everymagicseed'
USER_ID='8798'
USER_BET_NUMBER='73'
require 'digest/sha1'
# generates bet hash string
bet_hash = Digest::SHA512.hexdigest (SECRET + ':' + USER_SEED + ':' + USER_ID + ':' + USER_BET_NUMBER)
# bet_hash = '49dde939d58d494f4dbb3a510b86abe4f62d2c17a6a83bb3f5f9991a47cdac77b38008f8caf6938c6e491e6fd54ab020b1b961c787fd296cad4b2cae4ce540f6'
# pass hash to Mersenne Twister
print 'bet_hash: ', bet_hash, "\n"
@random = Random.new(bet_hash.to_i(16))
deck = ['AS', '2S', '3S', '4S', '5S', '6S', '7S', '8S', '9S', '10S', 'JS', 'QS', 'KS',
'AH', '2H', '3H', '4H', '5H', '6H', '7H', '8H', '9H', '10H', 'JH', 'QH', 'KH',
'AD', '2D', '3D', '4D', '5D', '6D', '7D', '8D', '9D', '10D', 'JD', 'QD', 'KD',
'AC', '2C', '3C', '4C', '5C', '6C', '7C', '8C', '9C', '10C', 'JC', 'QC', 'KC'] * 8
# shuffle deck
deck.shuffle!(random: @random)
# now deck contains shuffled deck
print deck, "\n"
and it outputs this: bet_hash: 49dde939d58d494f4dbb3a510b86abe4f62d2c17a6a83bb3f5f9991a47cdac77b38008f8caf6938c6e491e6fd54ab020b1b961c787fd296cad4b2cae4ce540f6
["7C", "4D", "2S", "10S", "9C", "8H", "AC", "5H", "3H", "6S", "9S", "8D", "5C", "7C", "3H", "9H", "QH", "2S", "8S", "9H", "KH", "4S", "9S", "8C", "KS", "5S", "7C", "4S", "QS", "QC", "10H", "JH", "JH", "KS", "7D", "7D", "6C", "QH", "4S", "4D", "7H", "KS", "AS", "3C", "2S", "AS", "QH", "8H", "7S", "3C", "5D", "2D", "5D", "JD", "QS", "JD", "QS", "9D", "9D", "2D", "JH", "2C", "9C", "2D", "7H", "6C", "8C", "7C", "8S", "JD", "7S", "9H", "3S", "8S", "7S", "4H", "7D", "8D", "6S", "KH", "AC", "QD", "KH", "QC", "3D", "3S", "8H", "3D", "3H", "4C", "QS", "QS", "6D", "9H", "8S", "JD", "AC", "3D", "JH", "4S", "5D", "2D", "AH", "7S", "3D", "6S", "5S", "5C", "QD", "8C", "5C", "KC", "6C", "4H", "AD", "KS", "5C", "7C", "5D", "7H", "AD", "JD", "2D", "4S", "6H", "3H", "2C", "6S", "QD", "6D", "QS", "AD", "5S", "3H", "AD", "6H", "9H", "8S", "3C", "2H", "2H", "6C", "5D", "7S", "2H", "QC", "4D", "9S", "6H", "7H", "JS", "6S", "8H", "KD", "6C", "6D", "7D", "10C", "10S", "QD", "9D", "2D", "QD", "2C", "4D", "10H", "9D", "3C", "AC", "KC", "KC", "8C", "JS", "QS", "6D", "9H", "JC", "3C", "KD", "7S", "JS", "10C", "8S", "5H", "6C", "6H", "5H", "2H", "2S", "4C", "9D", "2H", "3D", "JC", "JH", "AS", "AS", "9D", "5H", "KS", "KH", "3H", "AD", "8H", "8H", "3C", "10C", "5S", "10C", "3S", "6H", "5D", "AD", "5H", "9C", "4H", "KH", "4H", "10D", "2D", "JH", "3S", "10H", "7H", "10D", "AC", "JH", "6D", "QC", "6H", "10S", "4S", "4C", "AH", "10C", "4D", "10S", "JC", "10D", "5C", "8C", "KD", "AH", "KD", "4H", "10D", "KC", "AH", "KD", "8D", "7H", "8H", "10H", "AH", "6H", "QH", "4D", "9S", "5H", "10D", "9C", "8S", "2S", "3D", "10H", "JC", "8D", "QC", "7D", "JS", "JD", "7D", "JS", "7C", "4C", "6H", "9H", "4C", "8H", "KS", "8D", "QC", "2S", "4S", "10H", "8D", "QC", "4H", "JS", "8C", "10C", "5S", "AC", "6D", "9C", "10H", "3C", "9D", "5C", "2C", "6S", "5H", "JC", "AH", "9S", "KC", "AS", "9S", "5H", "5S", "AD", "10D", "6D", "AS", "KD", "5S", "6S", "3D", "4C", "AH", "8C", "5S", "AS", "10D", "9D", "10H", "JH", "4H", "7H", "7H", "JD", "5C", "JS", "6C", "AS", "QS", "10D", "9C", "KC", "5D", "9H", "2H", "4C", "QD", "AC", "2C", "9S", "7D", "2C", "2C", "9C", "2H", "2C", "5D", "QH", "JS", "3H", "3H", "9C", "KD", "10S", "AH", "4S", "KH", "QH", "QH", "10S", "QD", "10S", "KH", "KD", "6C", "KS", "JC", "4C", "4D", "4D", "2S", "2S", "4H", "QH", "3C", "7S", "3S", "3S", "KC", "JD", "6D", "KS", "JC", "QC", "8C", "2D", "7C", "3S", "5C", "KH", "QD", "7S", "AC", "7C", "8S", "10S", "AD", "8D", "7D", "2H", "8D", "3S", "10C", "6S", "KC", "JC", "9S", "10C", "3D"]
Note that the 'bet hash' is the same as I see when I click the bet ID: so at least the sha512 part of the code is getting the right hash. But I don't see how the final shuffle corresponds to the cards I was dealt. My first card was 9C, but there's no 9C near either end of the shuffled deck output. What am I doing wrong now? Maybe the Ruby code in the FAQ could be improved so that it will actually run and give the same shuffle as the game is using. I will check the soft 17 bug, with validation here's the correct code: require 'digest'
SECRET='7fc84a2d8dbf0d50b79bd771677354dd85b1b64129f6f54f7fb4def6973aba2598044eaa826a6020d41be7ec255e88b43c1b0afc2522c657aa6922b7852414d6'
USER_SEED='everymagicseed'
USER_ID='8798'
USER_BET_NUMBER='73'
deck = %w[AS 2S 3S 4S 5S 6S 7S 8S 9S 10S JS QS KS AH 2H 3H 4H 5H 6H 7H 8H 9H 10H JH QH KH AD 2D 3D 4D 5D 6D 7D 8D 9D 10D JD QD KD AC 2C 3C 4C 5C 6C 7C 8C 9C 10C JC QC KC AS 2S 3S 4S 5S 6S 7S 8S 9S 10S JS QS KS AH 2H 3H 4H 5H 6H 7H 8H 9H 10H JH QH KH AD 2D 3D 4D 5D 6D 7D 8D 9D 10D JD QD KD AC 2C 3C 4C 5C 6C 7C 8C 9C 10C JC QC KC AS 2S 3S 4S 5S 6S 7S 8S 9S 10S JS QS KS AH 2H 3H 4H 5H 6H 7H 8H 9H 10H JH QH KH AD 2D 3D 4D 5D 6D 7D 8D 9D 10D JD QD KD AC 2C 3C 4C 5C 6C 7C 8C 9C 10C JC QC KC AS 2S 3S 4S 5S 6S 7S 8S 9S 10S JS QS KS AH 2H 3H 4H 5H 6H 7H 8H 9H 10H JH QH KH AD 2D 3D 4D 5D 6D 7D 8D 9D 10D JD QD KD AC 2C 3C 4C 5C 6C 7C 8C 9C 10C JC QC KC AS 2S 3S 4S 5S 6S 7S 8S 9S 10S JS QS KS AH 2H 3H 4H 5H 6H 7H 8H 9H 10H JH QH KH AD 2D 3D 4D 5D 6D 7D 8D 9D 10D JD QD KD AC 2C 3C 4C 5C 6C 7C 8C 9C 10C JC QC KC AS 2S 3S 4S 5S 6S 7S 8S 9S 10S JS QS KS AH 2H 3H 4H 5H 6H 7H 8H 9H 10H JH QH KH AD 2D 3D 4D 5D 6D 7D 8D 9D 10D JD QD KD AC 2C 3C 4C 5C 6C 7C 8C 9C 10C JC QC KC AS 2S 3S 4S 5S 6S 7S 8S 9S 10S JS QS KS AH 2H 3H 4H 5H 6H 7H 8H 9H 10H JH QH KH AD 2D 3D 4D 5D 6D 7D 8D 9D 10D JD QD KD AC 2C 3C 4C 5C 6C 7C 8C 9C 10C JC QC KC AS 2S 3S 4S 5S 6S 7S 8S 9S 10S JS QS KS AH 2H 3H 4H 5H 6H 7H 8H 9H 10H JH QH KH AD 2D 3D 4D 5D 6D 7D 8D 9D 10D JD QD KD AC 2C 3C 4C 5C 6C 7C 8C 9C 10C JC QC KC]
bet_hash = Digest::SHA512.hexdigest (SECRET + ':' + USER_SEED + ':' + USER_ID + ':' + USER_BET_NUMBER)
random = Random.new(bet_hash.to_i(16))
deck.shuffle!(random: random)
p deck
|
|
|
|
|
Show Posts
