I propose to change the method of nodes’ voting by adding the opportunity to vote AGAINST besides the opportunity to vote FOR. Thus, all nodes that for some reason do not want to participate in the voting and do not write anything in the config file will not be taken into account when counting votes. It is fair and logical to exclude from the vote nodes irresponsibly related to events occurring on the platform.
Agree. Awesome idea.
It’s not a great idea, it makes node owners even lazier and care even less, because why should they change config, they vote for it anyway.
Also a while ago waves had feature 4 inside mainnet, but this couldnt be activated. So when everyone would automatically vote FOR something, errors and forks happen lot faster
I do not understand you. What is the problem with voting AGAINST as like you vote FOR? Feature will not activated automatically because of many blocks signaling needed. If voting longs a week and only one node signaled FOR activation, but others didn’t signal anything, so it must be activated IMO. Do not forget that any new features are legit because of coming from official team.
Totally supporting proposal. Not voting at all means you don’t care it’s like in usual housing business, where most of home owners does not care of the outcome and will follow the majority.
For the node owners to do the restart is no problem at all to add vote in favor or against the option, and only votes which are signed as favor or against are calculated and then required threshold checked.
Example, total blocks 10k, 6k votes in favor, 1k votes against, 3k didn’t vote, would mean that total amount of votes given is 7k and that would mean that 85,7% of votes were in favor and option is accepted. Presently in such situation it would be only 60% of votes in favor and feature wouln’t be accepted.
I think, before voting for a new feature, it needs to be carefully studied. By default, voting for everything is a bad idea.
The point of this proposal is to force pool owners THINK about new features. And mange the pool’s config. If people don’t like pool’s votes - call waves back from leasing and send to some more active pool.
By the way:
We invite all HODLERs to lease their Waves to us.
Briefly on the conditions:
100% of the fees for mining go into payments;
In addition to Waves and MRT we distribute a partner’s tokens equal $150. Sell it o HODL - you decide.
We have more than 80 000 Waves in the pool and we are keep growing up. Join today and get your WAVES, MRT (if someone will start to distribute them, huh?) and expensive liquid partner’s tokens. Best pool offer on the market.
Again. Who told about voting FOR by default? I suggested to not vote AGAINST by default. In your case now is the same situation - I doubt that every who voting FOR features now has studied it before.
People can manage their waves between pools. This will show to some fat pools that people are not dumb. Community should vote by their waves, not lazy pools.
Good idea. Lease your Waves to Progressive Nodes. Stop stagnation
Totally agree. Monopoly and stagnation kill the network.
Are talking here already about limiting time of the lease?
Поддерживаю данную инициативу!
If you don’t vote for it you vote against it.
you got 2 options, support it or not support it.
I think it might be a good idea to extend Waves Activation Protocol so that node owners have to  set JSON to participate in vote and  set JSON to Vote.
So in addition to ‘supported’ we could have ‘participate’.
Nothing in conf or participate commented out > defaults to node not taking part in vote and not counted in total.
participate = [9,10]
(features 9 & 10 not voted for.)
participate = [9,10]
supported = [9,10]
(both features voted for)
participate = [9,10]
supported = 
(feature 9 voted for only)
And so on.
It is actually true, because there are people who actually prefer to the previous versions of a feature. An upgrade of a new feature can actually disappoint them. And there should be an opportunity for those who are against the new feature, who actually stays silent than voting. It should definitely not count as a silent support for the new features,
The idea was suggested in 2017, but now it’s 19, and still there’s no “against” function lol