I'm very interested and I will follow this.
The way I see it, this will function as a mix between a traditional bookie and a betting exchange such as Betfair or Smarkets. In H2H betting one side will be backing the bet and the other one will be laying.
I have a few questions about the project:
- How will you create liquidity for H2H betting? All big betting exchanges incentivize market makers and give them access to an API that allows them to give liquidity to the market which in order creates tighter spreads. Others use the API to implement betting bots, which at the end of the day also bring liquidity.
- Do you have deals in place with odds providers for vs. chain betting?
- Are you focusing more on US (baseball, basketball, hockey...) or Euro (soccer, horses) markets?
- What are the requirements for running a Masternode? Do you have any information available in this aspect? How will the Masternode settle the results of the events (is manual intervention necessary?)?
Hi there, to answer a few of these quickly, if you have more questions please join us on Slack at
slack.wagerr.comWe will not be adding liquidity to H2H through API's early due to our goals being focused on adding the ability to achieve partner-less direct chain betting.
The oracle masternode owners will have 3 options to pull data for odds and outcomes. Sport betting API tieins, Site scrapes, and manual entry.
Wagerr is completely decentralized, thus if we used a single odd maker or information source it would still have a single point of failure, just like other semi-centralized solutions.
Oracle Masternode requirements 25000 coins collateralized.
Uptime measured weekly 99% or higher
Sport data feed
Public IP with a forced network port number
Bandwidth to accommodate the volume of the api calls
As for how bets are resolved here is a snippet from the soon to be released white paper.
