Quote from: Janitor on April 26, 2014, 08:17:58 PM

Quote from: Kyune on April 26, 2014, 05:32:38 PM

Suppose quick draw lottery result N comes out at noon, and result N+1 comes out at 12:04:00. If, per notsoshifty's and phm's suggestion I can manage (as a major pool) to mine a block at 12:00:05 that includes a Chancecoin bet that I know will win if evaluated against result N, but include in that block a timestamp that is a bit before noon (maybe even well before noon, given phm's comments), how can the Chancecoin protocol absolutely ensure that my bet is evaluated against result N+1 or later?

So you're a large pool that is actually two large pools (each with a different system time)?
How does that work?

And as magician said time tolerance can be decreased.
There's no reason to tolerate significant skew, IMO.
However, resolution in the next block is a small price ot pay just to be on the safe side.

I think Kyune has described it perfectly. Much better than I did anyway.

No need for two large pools (or one large pool splitting itself into two). One large pool could do it by itself. Of course, unless it was willing to put into its blocks a timestamp that is out by four minutes (unlikely), it wouldn't be able to do it for every block it mined; but nor would it need to.

My original suggestion was to include the block hash into the mix (as the transaction hash is now). Would that work? Does it introduce other problems (e.g. a winning bet might become a losing bet if its original block gets orphaned)?