Sort:  

1. Went well:

  • Got rid of Steemit Inc!!
  • Development continued at a fast pace
  • Communities growth
  • Hive Fest

2. Went wrong:

  • Some good efforts in this space but still not enough marketing - ACTION ITEM: @guiltyparties and @lordbutterfly to keep working on it and achieve great results!
  • The community is not quick enough when it comes to reacting to phishing -- ACTION ITEM: @keys-defender to keep automating as much as possible, humans are slow! 🤖
  • PS. Not enough engagement on posts   :( - ACTION ITEM: create @thank-you-for-engaging(?) bot that automatically upvotes comments longer than X words on posts with less than Y comments - @gaottantacinque

3. Shout outs:

  • Good job to @guiltyparties and @pfunk for always being on top of any abuse going on on Hive and for constantly finding ways to help Hive grow!
  1. What you think went well

a. managed to change the chain id
b. successful migration of most of the community

  1. What you think went wrong or should be improved

a. Have not managed to fully close attack vector --ACTION ITEM: Reduce witness votes per user to 8 (game theory), or have witness vote power be divisible by number of votes cast.

b. EIP reward curve still stupid -- ACTION ITEM: put it back to linear and let stake reward comments or posts however they want.

  1. Shout outs (feel free to tag any users that you think should know that they are doing a great job!)

Shout outs to @taskmanager, @raymondspeaks, @josephsavage, @rycharde, @gerber and @khaleelkazi for working diligently on great projects!

  1. Went well:
  • Got rid of Steemit Inc!!
  • active community with a desire to grow
  • New developers have approached our chain
  1. Went wrong:
  • Proxy system, witness votes, exchange of votes
  1. Shout outs:
  • To the whole community that makes Hive HIVE!

Thanks for your feedback @phage93. Could you please elaborate on the negative points?

Of course, currently the proxy system is the most used both from the point of view of the vote on the witness and as regards the path of voting trails. This is because many users and old investors, have moved away from the platform drawing only the benefits of automating as much as possible their actions on the chain. This involves a large amount of voting in the hands of a few and the impossibility of having a fair reward distribution.
I’ll leave you a screen of the various proxies:

proxy.PNG

tnx to arcange https://hive.arcange.eu/witnesses/

As for the exchange vote also it is present both in the witness landscape and in that of the blog. Needless to mention who and how, through hive.arcange.eu and other tools, you will see many interesting things.
there is the bernie' witness still active(innerhive), and five witnesses under the top 50 who haven’t updated the price feed in years, are still all vote given by the accounts on the steem chain, which have been inactive for years.

Thank you for your detailed explanation.

Do you envision any possible solutions?
Eg.

  • a proposal to make inactive witnesses lose their rank.
  • have proxies only accept X users and with a good balance of age of the account and reputation. These could be automatically and periodically rotated as well.
  • automated warnings added to frontends for users that constantly circle jerk?

As for the part of the witnesses, on a post of @blocktrades a few weeks ago, it was said that there would be some sort of cleaning up on the old votes given, ( older than a year I seem to remember) But I don't know if the speech was more touched or carried forward, as you can imagine would mean a nice nuisance, for those who are there to do farming without doing anything...

(surely a moderate view where there can only be x proxies or only a value of x would be a better compromise)

Some alerts could be inserted why not ... on hive.blog there would be plenty of nice things to implement ... consider that practically nothing has changed between now and 5 years, only the community part ...

The code for expiration of old votes has been completed and will be included in hardfork 25.

Thank you for your answer!

Hey @blocktrades, do you have a post detailing the business logic for the expiration of votes?


But yeh peakd did the flippening a few months back.Right, I think that only @quochuy has actively been working on it. He added a few nice features.

I'm slowly adding more features introduced by Peakd and Ecency. More can also be done if the backend (Hivemind or API) is also updated.