So I have been planning on setting up a masternode since the ICO. It was a high risk investment for me at the beginning, not knowning what it would turn out to be.
I do however see great potential. For me this is one the first true useful implementations of the blockchain.
Over the past few days I have taken the time to have a thorough look at the whitepaper. My prime interest is to see what it takes to setup a functioning masternode.
I'm not talking about the 25k WGR investment, that's a given. This is about the technology requirements behind the masternode.
It's good to see that others (@Spartaneous) are also asking technical questions. From what I read, Wagerr is relying heavily on the implementations of masternodes to become a success.
Another thing I'm interested in is the progress by the development team and the supposed 15jan mainnet release. But I will dedicate a seperate post on that topic.
So, I have a couple of technical/implementation questions;
1)@Spartaneous started of with a good one;
2) Does every masternode get the same requests or are some masternodes responsible for certain results and some others for other results?
Answered by @lotuspod with;
It's still a bit early for some specifics, ... these sources most likely will be randomly assigned to each MN.
One of the risks with WGR is that if someone has sufficient funds, they could get the 75% majority and decide the outcome for each game on the WGR network. In the whitepaper this is downplayed by the fact that making abuse of such a majority would probably have negative effects for the investor that holds 75% or more masternodes. Nonetheless, this is a potential risk.
With the answer provided by @lotuspod however, this potential attack vector suddenly becomes a lot bigger. Although from a technical standpoint I do understand that you may not need or want to have all results polled against every masternode, not doing so would inherintely increase the risk that someone has a 75% majority on a given result.
I wonder what the thoughts of the Wagerr team are on this.
2)I'm planning on writing a NodeJS scraper, or possibly implementing something using
https://xible.io.
So, to implement this, some kind of API docs must be available which explains the interface to the masternode.
This question will also be part of my next post on that 15jan release; but how can those docs not already be available if the release is so close?
3)Will every masternode be expected to return results on every league as part of WGR right now? That's a fairly long list already and from a developer standpoint it would be nice to be able to opt-in or opt-out for some leagues. Especially in the beginning, where a developer will probably implement a scraper league-by-league or site-by-site (where a single website may hold multiple leagues).
But, although this would be nice from a developer point-of-view, the earlier mentioned majority risk becomes an issue yet again...
4)What will the interface look like for manual input into the masternode? Any screenshots of current beta's? (again part of my next post on development progress)
5)Since I'm afraid that no docs will be available until the 15th, or perhaps even after that, we cannot expect that masternode developers have their end of the spectrum ready to go.
Manual input probably won't be an option as no one will have someone 24/7 behind a desk and results are expected to roll in within the hour after an event.
So will masternodes also be dropped in the early beginnings of the Wagerr (test?)net if they do not comply to the rules as they are currently set?
That's it for now.
Thanks!
