Now things get fun
redblocks.supertestnet.org



It defines the "Yes" condition based on a mix of timestamp ("11:59:59 PM") and blockheight ("the BIP-110 activation point"). But since those are not always in sync on bitcoin, there's a chance that we simply haven't reached that blockheight yet when we reach the timestamp when the measurement is supposed to happen.
In that case, the Yes condition would obtain unexpectedly: if we are only at block 965660 at the timestamp, instead of 965664, then -- at the time of measurement -- there won't be any "blocks that violate BIP-110 constraints" from BIP-110's activation height forward...but only because we haven't reached that blockheight yet.
So a person who thinks BIP110 won't activate might find it reasonable to bet Yes anyway, because even if BIP110 never gets enforced, you can still win if blocks just get slower than we currently expect them to.
Link to the market:
The website creates three characters, Alice, Bob, and Carol. Alice runs a "standard" bitcoin node that ignores the BIP110 soft fork. Bob runs a node that enforces the BIP110 soft fork. Carol runs a node that rejects the BIP110 soft fork. Then you pick how many miners enforce the rules of BIP110, from 0% to 100%. Then you generate blocks based on that assumption, and see how the blockchain looks on Alice's node, Bob's node, and Carol's node.
Try it here:


