******TEMPORARY RETRACTION*******
I expected you to say something like this.
I do want to be fare so in response I give the following:
I am aware of the definition of 'Gambling.'
I am not a soar looser and I accept the risk with full and total cognition.
I have a much higher IQ than average and have a perticular talent for pattern recognition.
I will tell you that I tested this many times.
When betting at 25% or less I would rarely incounter triple 0x's.
When placing new bets at 50% I would get trip 0x's each and every time.
With each bet I hit the 50% button leaving me with half of whatever I had left.
After awhile I would lower my betting percentage, build up my betting fund and try again.
I did this at least 10 times always with the same effect.
The 'loosing streak' was consistant when placing a new 50% bet /w trip 0x's or more in a row right out of the gate and a higher than usual number of 0x's over all.
When placing bets for 25% or less the number of wins normally out weighed the number of losses. (note: Total number of bets is not equal to the total value of bets, the overall trend is allways towards a loss when you gamble at truly random games)
Either the site is cheating or there is a bug that sets/resets some value when pressing the 50% button and this 'setting/reseting'
seems to ensure trip 0x's. [
edit: I also am considering that it is possible that there is some stored value that is unique to either my pc, ip, account #, logon session, system clock, etc.. that had an effect. If this were a factor it may not be possible to reproduce but is something to consider while checking the code and maybe changing the code so that it can not be a factor.]
I must admit that it is possible that this effect (or some variation) may occur each time you change your bet either by pressing any %age button, manally with the slider or by direct input. If this is the case it may not be noticed at lower betting rates because you are less likely to reset your betting amount, this
could be done intentionally or it
might just be the result of a coding error.
It is common to have bugs in ones code that only manifest when many people use the software. This is due to the fact that human behavior is often more random than one might imagine. People often do unpredictable things with a programers software and the higher the number of users the higher the number of unpredictable manipulation of input to the software. With the added condition of rapid resubmision of input the exponential gowth of unpredicted interactions with the software makes it near to impossible for a programer to produce an error free product.
In addition, I will admit that it is entirely within the realm of possibility that (due to the nature of randomness) I experienced an out of the ordanary event known as 'double clustering' were two instances that have a low probability occur relatively close to one another, giving me the impression that I received.
Considering these facts and in all farness I will admit that I may have made a hasty and unfair judgement (not my typical response) so I
RETRACK my accusation of cheating for now.
My suggestion is that you check to see if this is an issue in your code and that you not only test this for yourself but that you have
MANY people who do not have a vested interest in SatoshiCircle test this with dummy accounts (perhaps with a nice reward to encourage participation.)
I have started another thread for you and anyone else to post results of any testing done, just click this line to go there.EDIT: I actually
want to be wrong and I hope everything is just fine, but perhaps I have stumbled on an issue that you weren't aware of and knowing about it will help you make a better service for your customers. Good Luck!
We appreciate your detailed message and will consider your suggestions. Thank you for the retraction.
change the SHA Hash thus the result can not be tampered with.
Thanks.
