Hi @cwow2,

You are quite right. This particular issue (and many others like it) has been going on quite long enough...

In answer to your question:

These sorts of issues need to fall on the collective minds of the whole blockchain in order to avoid all the human derived problems that stem from this method of implementing Hive integrity.

Isn’t that what blockchain is supposed to be innovating? Consensus? Then why aren’t problems like these being dealt with within an actually predefined process that utilizes DPOS therefore mitigating high levels of stress to the community and the devaluation of the Hive Tokens price. (Yes. I would argue that this is indeed effecting our bottom dollar let alone the social health of the digital environment)

This is a governance problem... and so we need to be dealing with it appropriately.

The trust of our blockchain is at stake and this isn’t happening privately... it’s happening on the public stage and the whole crypto community is watching to see what and how we innovate next.

Relying to heavily on a crack troop of enforcement humans isn’t going to yield a friendly marketable solution. It’s going to do what it’s always done since human history began... get messy.

So again I say... this is a problem for the entire community to solve. And that’s the best thing about Hive. It’s got DPOS. Why not make use of this utility at the base level to solve this problem?

If we don’t take it seriously now... it’s only going to get worse as we attempt to scale and market Hive out to the wider population.

We can only contract so long... eventually we need to take a breath!

For more about what I’m thinking might work in regards to the DV’s implementation...

Here’s a link to @theycallmedan’s post a couple months ago.

My thoughts about DV’ing can be found near the top of the comments. 👇
@theycallmedan/a-bit-of-a-rant

Thanks for inquiring my friend. Your curiosity and willingness to ask mean a lot to me.

@wil.metcalfe