SlickTheNick (OP)
|
|
November 18, 2013, 04:41:57 PM |
|
Anyone have any suggestions for features, things to change or improve on for next version?
You forgot to revisit your "provably fair" method (good that you also used quotes for that, as it is false). There are two points that definitively defeat the fairness, and another one that does too but after clarification might be fine. You still have not made any mention as to how exactly it isnt provably fair... and for the record I do plan on revisiting it anyways, but like most people, I also have to work, plus I have several projects on the go. Only so many hours in the day my friend
|
|
|
|
SlickTheNick (OP)
|
|
November 19, 2013, 07:56:41 AM |
|
Brought an additional dev onto the team, working on some major updates as we speak! Stay tuned and lets keep the money flowing
|
|
|
|
birkomester
|
|
November 19, 2013, 05:23:02 PM |
|
Great site, already won some btc.
|
|
|
|
SlickTheNick (OP)
|
|
November 20, 2013, 01:12:48 AM |
|
Great site, already won some btc.
Great to hear! We will be adding 3 additional coins to buy, as well as adjusting the increase rate and reset chance values for the existing coins. So there will be several levels of play, and more chances to win!
|
|
|
|
moderate
Member
Offline
Activity: 98
Merit: 10
nearly dead
|
|
November 20, 2013, 01:31:53 AM |
|
Since there is no effort in understanding why this is not provably fair, here is the first place where it fails:
A random number between 0 and 1000 (known as a "nonce")
This is also the first step of your method.
To the owner: before you reply saying this is false and doesn't make it not provably fair, take at least some minutes to think about it.
|
|
|
|
SlickTheNick (OP)
|
|
November 20, 2013, 01:44:08 AM |
|
Since there is no effort in understanding why this is not provably fair, here is the first place where it fails:
A random number between 0 and 1000 (known as a "nonce")
This is also the first step of your method.
To the owner: before you reply saying this is false and doesn't make it not provably fair, take at least some minutes to think about it.
not entirely sure why you seem to be trying to start an argument here.. I said it was provably fair, but I didnt say that your claim that it wasnt is false. I just asked how you came to that conclusion. I have been putting thought into it, I just havnt posted about it yet. Here is what im thinking for updating the provably fair scheme: - Use the first 5 characters or something of the bet transaction ID as the nonce, rather than a simple server side generated random number
- Changing the "coin flip" (decide wether target is high or low) to be based on something not controlled by the server... not sure what yet though
- Hashing the client seed on the client side, before its sent to the server
What do you think?
|
|
|
|
moderate
Member
Offline
Activity: 98
Merit: 10
nearly dead
|
|
November 20, 2013, 01:52:12 AM |
|
Since there is no effort in understanding why this is not provably fair, here is the first place where it fails:
A random number between 0 and 1000 (known as a "nonce")
This is also the first step of your method.
To the owner: before you reply saying this is false and doesn't make it not provably fair, take at least some minutes to think about it.
not entirely sure why you seem to be trying to start an argument here.. I said it was provably fair, but I didnt say that your claim that it wasnt is false. I just asked how you came to that conclusion. I have been putting thought into it, I just havnt posted about it yet. Here is what im thinking for updating the provably fair scheme: - Use the first 5 characters or something of the bet transaction ID as the nonce, rather than a simple server side generated random number
- Changing the "coin flip" (decide wether target is high or low) to be based on something not controlled by the server... not sure what yet though
- Hashing the client seed on the client side, before its sent to the server
What do you think? Good that you pointed the target being high or low, as that is another problem. The final problem, that requires clarification, is defining very clearly how you pick the unix timestamp of time of purchase. So we agree that currently you have 3 flaws, so it is not provably fair. Right ? You should just check out what Satoshi Dice does (the legacy version) and base on that.
|
|
|
|
SlickTheNick (OP)
|
|
November 20, 2013, 02:06:04 AM |
|
defining very clearly how you pick the unix timestamp the time() function...? what else would you suggest? Actually the timestamp recorded in the bet transaction could work
|
|
|
|
moderate
Member
Offline
Activity: 98
Merit: 10
nearly dead
|
|
November 20, 2013, 02:12:04 AM |
|
defining very clearly how you pick the unix timestamp the time() function...? what else would you suggest? Actually the timestamp recorded in the bet transaction could work If you are using time() (or any other OS-related function) then that confirmed my suspicion, that is not fair in any way, even if you tried to. So yes, you need a timestamp that is publicly recorded if you want to continue using it. The previous suggestion stands.
|
|
|
|
SlickTheNick (OP)
|
|
November 20, 2013, 02:13:41 AM |
|
defining very clearly how you pick the unix timestamp the time() function...? what else would you suggest? Actually the timestamp recorded in the bet transaction could work If you are using time() (or any other OS-related function) then that confirmed my suspicion, that is not fair in any way, even if you tried to. So yes, you need a timestamp that is publicly recorded if you want to continue using it. The previous suggestion stands. duly noted.
|
|
|
|
moderate
Member
Offline
Activity: 98
Merit: 10
nearly dead
|
|
November 20, 2013, 02:22:15 AM |
|
defining very clearly how you pick the unix timestamp the time() function...? what else would you suggest? Actually the timestamp recorded in the bet transaction could work If you are using time() (or any other OS-related function) then that confirmed my suspicion, that is not fair in any way, even if you tried to. So yes, you need a timestamp that is publicly recorded if you want to continue using it. The previous suggestion stands. duly noted. Hopefully not in this manner: http://www.urbandictionary.com/define.php?term=duly%20noted&defid=7088701
|
|
|
|
SlickTheNick (OP)
|
|
November 20, 2013, 02:25:20 AM |
|
defining very clearly how you pick the unix timestamp the time() function...? what else would you suggest? Actually the timestamp recorded in the bet transaction could work If you are using time() (or any other OS-related function) then that confirmed my suspicion, that is not fair in any way, even if you tried to. So yes, you need a timestamp that is publicly recorded if you want to continue using it. The previous suggestion stands. duly noted. Hopefully not in this manner: http://www.urbandictionary.com/define.php?term=duly%20noted&defid=7088701A phrase meaning "to understand". "Kim I love your shirt, but it looks a little small on you." "Duly noted."
|
|
|
|
SlickTheNick (OP)
|
|
November 21, 2013, 08:06:58 AM |
|
Added 3 additional coins to purchase, and adjusted the coin values so there are several levels of play. From 1 BTC all the way down to 0.000055 BTC, and 75% to 99% chance to get your money back plus profit. Going to release a design/front end update within the next few days, and also update/improve the provably fair scheme over the weekend.
Great first week!
|
|
|
|
Stake
Newbie
Offline
Activity: 56
Merit: 0
|
|
November 21, 2013, 08:08:59 AM |
|
I like the idea I think it could work better.
I think this will be successful.
Good job.
|
|
|
|
SlickTheNick (OP)
|
|
November 21, 2013, 08:46:27 AM |
|
I like the idea I think it could work better.
I think this will be successful.
Good job.
Thanks, any suggestions in particular?
|
|
|
|
SlickTheNick (OP)
|
|
November 24, 2013, 02:50:10 AM |
|
Just updated the site! Another update coming probably sometime tomorrow which will tweak some things, add the timer back in and add some other effects. Great weekend so far! Here are the changes: - update game design, much less 'scrolly' now, looks a little nicer
- Fixed some issues with the mobile version, purchase form is now actually usable when on a phone
- Updated the reset/increase values for each of the coins. added an experimental "magic" coin where you can double your money each turn
- Improved the provably fair scheme to be more fair... timestamp is now taken from your bitcoin transaction, nonce is taken from your transaction ID, and the "coin flip" is determined by the time your transaction was included in the blockchain (blocktime). See how-to-play for more details
More updates still on the way, stay tuned. Any feedback is appreciated.
|
|
|
|
tim13n
Member
Offline
Activity: 74
Merit: 10
|
|
November 25, 2013, 10:01:50 PM |
|
Nice website!
Tested and Aprouved !
|
|
|
|
Malongo
Newbie
Offline
Activity: 42
Merit: 0
|
|
November 25, 2013, 10:17:07 PM |
|
Something is wrong there.. When i open the Website...this happens all the time http://abload.de/thumb/coincontrollervhjjj.jpgI can't close the window or anything else...it stays just like that
|
|
|
|
tim13n
Member
Offline
Activity: 74
Merit: 10
|
|
November 26, 2013, 12:06:59 AM |
|
Works perfectly form me ! now !
|
|
|
|
Malongo
Newbie
Offline
Activity: 42
Merit: 0
|
|
November 26, 2013, 12:43:03 AM |
|
YEP ! No probs anymore! Don't know, if it was sth here or there..whatever..Works perfect
|
|
|
|
|