Quote from: BTCDice on October 20, 2012, 03:48:42 AM

Quote from: mem on October 20, 2012, 02:20:23 AM

Quote from: 22bones on October 19, 2012, 09:54:01 PM

I was using bitcoind to send directly to the address. I can't verify all of the games until more than 24 hours has passed, since the site uses the time of processing to choose the secret used (which it shouldn't, it should use the time recorded in the block chain for the transaction).

I don't know what you mean by "independent," I lost 21 games consecutively. If we round the <32k game to 50% chance of winning, it's like a coin flip, where the chance of flipping heads is 1/2^1, or 1/2. The chance of flipping 2 heads in a row is 1/2^2, or 1/4. That would make my run of 21 losses about a 1/2^21 chance, or 1/2097152.

red flag

The site operator can easily delay processing transactions until the current time generates a losing secret.
Please use the blockchain timestamp.

None of transactions were delayed. I have two way of processing on transaction, either live transaction or re-queue (during heavy load, or follow downtime), both of which use timestamp for the day that bet was processed. Edit to make clear: ("processed" meaning, when TX was broadcast through bitcoin on server)

Individual timestamp does not matter, only the day of timestamp. Does not matter if transaction occur at 23:59:59 on 2012/19/10 or at 00:00:01 on 2012/19/10, it will use same secret.

You can verify transaction yourself once secret is revealed.

If you claim this is red flag on me, you claim it is red flag on Satoshidice too, because Satoshidice works same way.

Thank you for clarifying that, that was my only concern.
I am further impressed you use the bitcoin time stamp to process the tx against the secret used at the time the bet was placed for delayed bets.
Very very good work.

GREEN FLAG