WINC WHITEPAPER
  • πŸ“š1.0 Abstract
  • πŸ’‘2.0 Manifesto
  • ❓3.0 Problem Overview
  • ⁉️4.0 Criteria for a solution
  • πŸ—οΈ5.0 Features and functions of Winc
  • πŸ’±6.0 Economics: Structural dynamics of Winc’s economic system
  • πŸŽ‡6.1 Value proposition for sports bettors
  • 🦯6.2 Value proposition for holders of WΔ°NC
  • πŸ’Ώ6.3 Value proposition for the sports betting industry
  • πŸ“€6.4 Value to investors
  • βš–οΈ7.0 Betting Engine & Technical Architecture
  • ⚽7.1 Head to Head Betting Process
  • 🀹7.2 Multi User betting
  • ⛓️7.3 Peerless Direct Chain betting
  • βš’οΈ7.4 Creating and Resolving events
  • ⏲️7.5 Time Related Conditions (Atomic Pairing)
  • 🀺7.6 Activating an Oracle Masternode
  • πŸ“½οΈ7.7 Promotion queue
  • πŸ“Ό7.8 Demotion
  • βš–οΈ7.9 Governance
    • πŸ“‡7.9.1 Payout dispute
    • πŸ“”7.9.2 Penalized nodes
    • πŸ““7.9.3 Oracle Masternode voting
    • πŸ“°7.9.4 Potential network threats
  • 🏈8.0 Sports data Feeds
  • ⛓️8.1 Network Add-ons & Enhancements
  • 🐌8.2 Scalability
  • πŸ’²8.3 Fee Structure
  • πŸ…8.4 Supported Leagues
  • πŸ’Ή9.0 TOKENOMICS
  • πŸ›£οΈ9.1 ROADMAP
Powered by GitBook
On this page

7.4 Creating and Resolving events

Once the event is completed, the Oracle Masternode network can begin to post the outcome data. An event outcome is confirmed only after 75% of all Oracle Masternodes achieve consensus on the outcome. Once the outcome is finalized and posted, the Winc network recognizes completion of the contract, and the winning user is paid out accordingly. Creating events is dependent on The Oracle Masternodes posting data that can be consensually verified. Winc achieves this through creating a unique means of structuring events and bets. Below you can see exactly how the bets will be posted and how unique events are distinguished as single events.

Previous7.3 Peerless Direct Chain bettingNext7.5 Time Related Conditions (Atomic Pairing)

Last updated 1 year ago

βš’οΈ