Pages:
Author

Topic: TossBits.com - toss a coin like game with variable payout. Provably fair (Read 1639 times)

hero member
Activity: 784
Merit: 1000
Casper - A failed entrepenuer who looks like Zhou
Got a decent profit in this dice game, deserve a bump Smiley
hero member
Activity: 784
Merit: 1000
Casper - A failed entrepenuer who looks like Zhou
It's still a dice game at 50%. Just a different payout.
And you are free to rip off losers and dont feel guilty, coz they "donated" it to the pool!
legendary
Activity: 3416
Merit: 1912
The Concierge of Crypto
It's still a dice game at 50%. Just a different payout.
hero member
Activity: 784
Merit: 1000
Casper - A failed entrepenuer who looks like Zhou
Just someextra suggestion that a  option for sound notification of bets in good so that we can bust another guys' game, more PVPness Tongue
hero member
Activity: 784
Merit: 1000
Casper - A failed entrepenuer who looks like Zhou
i guess we have found some genius busted Smiley

 time to clear em out
xyu
full member
Activity: 182
Merit: 100
the more you lose the higher probability to win

Sounds like gambler's fallacy to me.
Smiley
Maybe I wasn't clear enough: it is not the probability of winning is higher - it is always 50% it is the chances to win you money back because you decrease the bank in geometric progression.
full member
Activity: 196
Merit: 100
the more you lose the higher probability to win

Sounds like gambler's fallacy to me.
xyu
full member
Activity: 182
Merit: 100
another problem I see is that if a payout % is lower than 99% , why would I play at your site instead of just-dice for example that will always give me 99% return if I win?
Because it doesn't work like a dice game - that's the whole point, lets consider the following example:
We have a 1BTC bet, with the payout 50%, you may think that this is not a nice situation to get in the game, but actually you could have the following strategy
1. Ensure you have enough balance to make something like 5-6 bets (i.e. 5-6 BTC), lets say we have 5 btc
2. Start betting, if you have lost, bank will have 2 btc and payout will be 100% and you have 4 btc in balance
3. You can continue to bet, if you lost again you will have 3 btc in balance and bank will be 3btc and payout is 150%
4. As you can see bank and payout are heavily depend on the current streak if it is all loses - it will quickly grow, but if it all wins you can quickly recover all loses, and the more you lose the higher probability to win. Also bank grows in arithmetic progression and decreases in geometric.
5. Lets say you bet again and you win, you won 1.5 btc, your balance now is 4.5 btc and bank is 1.5 btc
6. You bet again and you won 0.75 btc and you balance will be 5.25 BTC - it is already higher than you had when you started!



So to sum up: in dice games it all about luck, here you can have some strategy, but because this is gambling no one guaranteeing that there is a strategy that will always make you money, for instance some dude could watch the site while you making these bets and he could just make a bet in between your bets and win.

And if this thing will take of, be sure it wouldn't be people who play it but bots. Lol, I was even thinking that I should take some time and release a bot at the same time with the game so that people will be equal in their chances Smiley But I already had a deadline for this thing a week ago, so I just had released it without any fancy bots Smiley
full member
Activity: 196
Merit: 100
Now wait for a genius to play the EV up

Oh, had nothing to do at work today so I played the 0.003 up to 225% and someone quickly took it Cheesy
sr. member
Activity: 293
Merit: 250
another problem I see is that if a payout % is lower than 99% , why would I play at your site instead of just-dice for example that will always give me 99% return if I win?
xyu
full member
Activity: 182
Merit: 100
The problem with this aproach, is that everytime I access your site I will have to check the code to see if you didn't change it. Will be way better if you implement a way for us to change it.
Yep. added to the todo.


The seed can't be global, but attached to the session. IMO, the best way to do it is to generate a seed to our session, show it to the user just before any bet, provide a way so we can set our client seed and after the bet generate another server seed to the next bet.

Okay, I'm gonna think on it.
hero member
Activity: 784
Merit: 1000
Casper - A failed entrepenuer who looks like Zhou
Now wait for a genius to play the EV up
full member
Activity: 196
Merit: 100
I agree with everything BRules said.

Nice concept of the site though!
sr. member
Activity: 322
Merit: 250
What happens if the bank gets so small that people don't want to bet anymore?
sr. member
Activity: 293
Merit: 250
Sorry, but I don't follow what you trying to say - have you found any significant flaw in this scheme compared to to others or you suggesting an better solution? We can't skip hashes from the batch, because they are taken sequentially

you can skip it by simulating a play before mine for example.

Quote
it is all embedded right into html and is not minified, so you can inspect the code.

The problem with this aproach, is that everytime I access your site I will have to check the code to see if you didn't change it. Will be way better if you implement a way for us to change it.

Quote
But it isn't in this scenario we could just easily fool you by using any seed that will make any outcome we want - just enumerate few random seeds that would give us desired outcome. Even if we would somehow publish a hash of this seed - you cannot be sure that hash you see is for the seed that you will get when you bet, since any other player might use this seed before you.

The seed can't be global, but attached to the session. IMO, the best way to do it is to generate a seed to our session, show it to the user just before any bet, provide a way so we can set our client seed and after the bet generate another server seed to the next bet.

xyu
full member
Activity: 182
Merit: 100
Why wouldn't it make sense to create a different server seed beforehand for each game and after it is used, immediately publish it?
Just wonder how will you check it? You decide to check our honesty - you check the client seed, remember it, you make a bet - and check what was the server seed - seems ok? But it isn't in this scenario we could just easily fool you by using any seed that will make any outcome we want - just enumerate few random seeds that would give us desired outcome. Even if we would somehow publish a hash of this seed - you cannot be sure that hash you see is for the seed that you will get when you bet, since any other player might use this seed before you.

But if a player uses that hash just before me, I could easily confirm this on the right side. Now you can say: doesn't prove anything since we could already do this.

Well with your current implementation you could also skip hashes from the batch and add fake bets to the right to compensate.
Sorry, but I don't follow what you trying to say - have you found any significant flaw in this scheme compared to to others or you suggesting an better solution? We can't skip hashes from the batch, because they are taken sequentially
full member
Activity: 196
Merit: 100
Why wouldn't it make sense to create a different server seed beforehand for each game and after it is used, immediately publish it?
Just wonder how will you check it? You decide to check our honesty - you check the client seed, remember it, you make a bet - and check what was the server seed - seems ok? But it isn't in this scenario we could just easily fool you by using any seed that will make any outcome we want - just enumerate few random seeds that would give us desired outcome. Even if we would somehow publish a hash of this seed - you cannot be sure that hash you see is for the seed that you will get when you bet, since any other player might use this seed before you.

But if a player uses that hash just before me, I could easily confirm this on the right side. Now you can say: doesn't prove anything since we could already do this.

Well with your current implementation you could also skip hashes from the batch and add fake bets to the right to compensate.
xyu
full member
Activity: 182
Merit: 100
Why wouldn't it make sense to create a different server seed beforehand for each game and after it is used, immediately publish it?
Just wonder how will you check it? You decide to check our honesty - you check the client seed, remember it, you make a bet - and check what was the server seed - seems ok? But it isn't in this scenario we could just easily fool you by using any seed that will make any outcome we want - just enumerate few random seeds that would give us desired outcome. Even if we would somehow publish a hash of this seed - you cannot be sure that hash you see is for the seed that you will get when you bet, since any other player might use this seed before you.
full member
Activity: 196
Merit: 100
Why wouldn't it make sense to create a different server seed beforehand for each game and after it is used, immediately publish it?
xyu
full member
Activity: 182
Merit: 100
I first read it incorrectly and assumed the batch hash was the hash of the next server seed, which is not the case.

Why did you take this approach instead of just publishing the hash of the next seed?
Do you mean kind of the server seed that changes, say, once a day and its hash published somewhere on the site?
Well, with this I should also make sure that you cannot use client seed twice, since it will be obviously exploitable, so I just thought making unique random seed for each bet would be more secure, the problem was that publishing hash of this seed wouldn't make much sense because it would always change with each bet, so I decided to combine them in batches and publish the hash of the batch.
Pages:
Jump to: