@steve2507
1) The majority issue is true for pretty much any blockchain, however accumulating 75% of the masternodes just to change some bet results and essentially ruin the chain...would simply be very impractical to the point of being nearly impossible. Besides that, I have a lot of trust and respect for the newly established Wagerr community as a whole. During the few rough months awhile back, a lot of the weak hands sold off and we were left with a solid core of very supportive members and many of which aren't very easily swayed by financial gain alone. Some of us have even been victims of all sorts of pretty shady practices by some of the centralized gambling networks, personally this has been my main motivation for wanting this project to succeed.
I also think I wasn't clear enough on how I explained it in the previous post, and it may have caused you to misunderstand. My main point wasn't that a subset of the masternodes would be randomly polled for results(I don't have details on that part yet but I made a note to try to get you all some), I meant that the actual results sources could be randomly assigned to masternodes so that everyone isn't using the same source or few sources...such that certain sources aren't too unfairly weighted. This is much more likely to pose a realistic security issue with the results, rather than someone buying out 75% of the masternodes. But even this isn't much of an issue, since if too many of the major results sources are incorrect a meaningful % of the time...then the sportsbetting industry as a whole would be having some serious issues
2) The reason that docs like you're referring to aren't out yet is that h2h and other types of betting won't be included in the initial mainnet release on Jan 15th. Instead, the masternodes will get at least half of the staking rewards and at least half of the transactions fees until mainnet h2h betting is implemented. We will have a few months to get familiar with the testnet first, and bring h2h over to mainnet when we all are feeling comfortable with it. I do agree with you that getting some of these related docs out as early as possible will be very helpful to the community and we'll try to get you the relevant info as soon as it becomes available to us.
3) I don't think you'll need to post every single league worldwide, there will likely be some sort of minimum requirements though to make sure each masternode contributes its fair share of the work. Sorry for having to give the same response so many times, but it's yet another set of details that I'm going to make sure to annoy the devs about for you guys and try to get back to you ASAP.
4) I really (really!) tried on this one to get some screenshots in the most recent email/news update, but I can't talk about these things specifically just yet
However I can say to keep an eye on this thread and our Discord/Telegram servers as we inch our way closer to mainnet release.
5) I wouldn't rule anything out quite yet, let me see what I can do
*Remember none of this is exactly set in stone yet, certainly not until I get some confirmations on those specific details that I'm unsure on and also hopefully get some documents and/or screenshots for you all within a reasonable time.
**The best place by far for you and others who are interested in running masternodes is the #masternodes-oracles channel on the Wagerr Discord server, if you aren't already there. Be sure to check the pinned messages in that channel for lots of interesting tidbits of info you may not have caught.
Thank you for your response! Although I do still have some questions on the technical side, I'll drop those on Discord.
However, the other point I'd like to address here is the scheduled 15 January release for test- & mainnet.
What I simply do not understand is the lack of 'marketing' surrounding Wagerr. Again, I'm planning on setting up a masternode so I have invested. But at the moment it's a coin toss for me. There's simply not a lot of information out there which supports any ongoing development efforts. Comments on this forum stating that some implementation details are uncertain at the moment do not really help either. With a planned deployment in <1month, those details should be clear. Testing is all that should remain, otherwise I sense an upcoming delay for the golive.
Here are some things I would expect from a team with a deadline right around the corner;
1) Proper introduction of the new developers that were hired
2) Weekly updates (youtube/blog/whatever) which may include; (this is by far the most important of the 4 points I mention here)
- developer interviews on their current focus and progress.
- discussion on the past and future of WGR
- comparison of WGR to other 'coins'
- technical details regarding the implementation of the new blockchain/DASH fork
- community input and discussion
3) API documentation (at least part of it)
4) Runbooks for setting up masternodes (at least a draft)
All of the above can give people a little bit more assurance than there is right now.
Please do not see this as an attack on the WGR team. Consider this to be constructive feedback on the marketing side of things which will hopefully improve in the near future.
Thank you!
