You are viewing a single comment's thread from:

RE: VOTE AGAINST the 4 week powerdown time reduction proposal.

in #proposal3 years ago

Currently 12 people against and it's 47%, 41 people for and it's at 14%.

Proving again and again that we're not as 'decentralized' as we think we are. Whales are gonna do whatever the fuck they want and the rest of us I guess just put up or shut up.

Sort:  

Its just Blocktrades and Neoxian that are against it out of the large accounts.

The problem is that the next HF will remove most of the witness votes due to inactivity so the witnesses (that are large accounts) are afraid to lose the Blocktrades vote so they dont want to go against him.
Thats why theyre silent. Even though many are in support of the proposal.

The community needs to step up if they want change. We would need a couple hundred smaller accounts for this to pass.

I like Blocktrades, generally, but I definitely don't agree on squashing the 4 week proposal. If weak hands want to exit - fucking let them!! Let's get them out as soon as we can, the price will recover and - if Steem is any indication - we'll be all the better for not having folks constantly keeping us stuck in the 50c range.

Just my two cents, as a nobody but, that's my opinion.

well here we are voting on time needed to power down stake. and we are voting with stake that needs to be powered down. so i feel people with a lot of stake should be able to have a bigger vote on what will happen with their stake.
is their decision right one no idea.
maybe blocktrades just does not want to add new code to the hard fork that is already in testing so that there is less possibility of something going wrong. because the HF code is already done and on test net. and coding something that is directly connected to our funds probably should not be rushed.

But nothing "happens" to their stake. Keep it powered up if you don't want to power down, it doesn't affect the current stake at all.

I do however agree that injecting anything on an already basically finished HF is silly.

if i remember blocktrades has no strong opinion on powerdown time, so he voting no right away makes me think he does not want to include any new code to this HF. especially something that is connected with stake and funds.
i know they moved resource credits code to after the HF just to not wait a week or two and change the finished code.

If that is the case I could understand for sure! My day job is QA so I definitely have had my fair share of 'lets just push this in last minute' blowing up in my face and pissing me off lol

That's nonsense! Read again this paragraph from above: "I have talked to one of the large Hive investors and a core team developer and it was made clear to me that adding this change into a future HF would not be too difficult and if the proposal passes the return proposal and the AGAINST proposal in votes, it would be accepted as a change the community/investors want implemented".
I understand that if @blocktrades has a lot of stake, his vote should be bigger, but I'm just asking him why he sticks to the 13 unstaking period. That's something of the past, when we all were on St--mit, but things change and most of the community, myself included, is wondering why we should keep carrying this burden. The majority of tribes have taken the 4 weeks approach because it's better for everybody. Why should Hive be different?
I really would like to see the small accounts needed to vote on this proposal to be approved, but unfortunately I don't think this is going to happen.

i don't know is it easy or difficult, but the code for HF is "freezed" two weeks ago and test net is running. and i seen some stupid code misses for hard forks when the chain was down for days. adding additional code would move the HF for more testing or maybe less testing. bug connected with funds is something i would not want to see.

i am not even sure that is the case, i think i read some post or heard in some talks that he has no strong opinion about 13 or 4 weeks powerdown, so this is my guess. and listening to hive development meetings i concluded he is not happy with adding new things after the testing is started. and i can understand that.

Ok, thanks for the info.