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.2 Multi User betting

To make it easier to find and fulfill more bets on low volume events, the system allows multiple players to be paired against a single bettor. This ensures that large bets do not require an exact match to forge a contract. The fee for this transaction is 4 percent. 2% of the fee goes to the Oracle processing the transaction and 2% gets burned. Here is the Flow of a multiple user bet from start to finish.

Previous7.1 Head to Head Betting ProcessNext7.3 Peerless Direct Chain betting

Last updated 1 year ago

🀹