⏲️7.5 Time Related Conditions (Atomic Pairing)

Betting closes 10 blocks before the event is scheduled to begin. Most contractual conditions surrounding bets are related to real-world time. Block times are dynamic, not static, while events are coded in Coordinated Universal Time (UTC). Block time closing in on bets being accepted is no later than 10 blocks before the event happens. (10 Blocks = 10:40:00) (target/approx) When a user posts a bet on the cusp of approximately the 10 minute mark, one of two events will occur on the blockchain, resulting either in contract formation (match and confirm), or transaction failure (in which case, the transaction would not be accepted, and the pre-bid coin locations remain unaltered). In order for the transaction to confirm, two conditions must be met: first, there must be a match between the amount of the initiating bet and the amounts of the complementary bets taking the other side. Second, the official time that the block containing this transaction is first confirmed on the chain (encoded in UTC time) must be prior to the T-minus-10 minute mark for the sporting event. In technical terms, “atomic pairing” is the synchronization of two conditions (the two sides of the betting contract) occurring at the same time. and the bet is taken, the bet is an atomic transaction (meaning that the transactions happen at the same time or in the same block) This ensures that the bets that are taken they get accepted and processed in time. It also ensures that users do not have to pay fees on bets that are never matched. The timeframe for a payout to take place will be a target time of 1 hour after the event outcome is resolved. Oracle Masternodes post data for all supported leagues every hour as long as Oracles are in agreement of the outcome the payout should take place no longer than 90 minutes after the event ends. In the event of a tie, push, or the event not taking place, the Oracle Masternode network will resolve the and confirm and initiate the return of the wagered amount back to the bettors original wallet addresses minus the betting fee. This process can take up to 24 hours to ensure the Oracle Masternode network has time to achieve consensus.