RE: Community communication of the code
You are viewing a single comment's thread:
This time not much “law” changes, with the exception of the 30 days witness voting lock on VP power, and as an aside almost the conversion of the DAO stake which starts.
I think the DAO one is pretty big - from the little I understand on it :D
Should we expect everyone to be able to dig through the code and discover the date when a HF is supposed to happen? Not everyone but maybe in a decentralized society this is one of those where many could discover (and build that countdown) and maybe should do just that.
I don't think it is useful to expect people to dig through code as users, but frontends have coders that can at least inform the basics to their users.
I think that for larger investors to come into the space, more visibility on what they are buying will be demanded.
I am going to guess this would have happened if the HF had an actual date, if this refers to the countdown.
If it refers to more, decentralized issues where the operators will decide whether providing that information is of value to... themselves. Will they slip out of the active witnesses (top20) if they don’t? Will it consolidate or strengthen their position if they do? Is the ROI worth the effort???
Technically not. By which I don’t mean code complexity wise, but that the decision to use that stake for the DAO was made when we forked away. No one submitted a HF which burnt that stake and as such that wasn’t really a topic beyond social media arguing.
In this fork the required mechanic to make the stake usable, within the DAO mechanics, is integrated. But AFAIK it doesn’t change the DAO or the level of daily available funds which stays at 1% of the available liquid DAO funds.
Yes, I’m thinking/arguing semantically here. On purpose. :D
But on a general level I do agree with the need for transparency and improved information.