RE: Gridcoin 4.0-2018 General Roadmap Poll - Solving the Stake Weight Problem

You are viewing a single comment's thread from:

Gridcoin 4.0-2018 General Roadmap Poll - Solving the Stake Weight Problem

in gridcoin •  7 years ago 

Your discussion is pretty clear about what changing to CBR would do, but doesn't outline what it would mean to have master nodes even though that is one of the poll choices. Would you please add a short discussion of how master nodes fit in with CBR?

Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE STEEM!
Sort Order:  

Excellent point. Those of us putting this together definitely succumbed to the curse of knowledge here -- we just had an extremely in depth conversation about masternodes so it did not even cross our minds to put a synopsis in this article!

I will see what I can do about adding a short description of masternodes before the end of the week. In the meanwhile, feel free to take a look at the at length discussion from last month here:

https://cryptocurrencytalk.com/topic/90700-gridcoin-future-technology-base/

The proposal was already turned down, however we do not want to completely dismiss the idea. It might be explored further in an open-source arena as opposed to an extremely centralized environment, which was a major complaint with regards to the original proposal. There are also many serious concerns with regards to masternodes expressed on that thread, including that once we implement masternodes, it will be incredibly difficult to implement any other technology base in the future (blockchain tech is still gestating!).

added a quick synopsis.

It's too large a change IMO, it would require rebasing and snapshot/sharedropping which would risk splitting the Gridcoin crypto in two. CBR > Masternodes.

Both rebasing and Sharedropping are still separately considered for future. Argument for rebasing is to get more maintained code-base. And for Sharedropping it is the removal of leaked historic data.