Witness Update @blue-witness - Re: Core Dev Meeting #7

My take on the Hive core developper meeting #7 update by @howo

Thoughts about the upcoming hard fork 24:

@blocktrades is arguing for only implementing business logic in the current fork and adding SMTs with a fork in the near future.

I like it for three reasons:

  • It cleans up boring infrastructure issues first.
  • The SMT hard fork should mainly be about SMT implementation. That sends a clear message to the outside world without being diluted by weird Hive particularities that nobody but we understands or cares about.
  • It makes it easier to attribute changes that will occur to their respective forks.

Sneaky minor fourth reason: I prefer frequent but minor forks over major, convoluted ones. It gets everybody used to a faster development cycle and makes changes and side effects more visible.


More ideas for a later date:

  • Adding downvote power delegations
    • Yes, please!
  • Adding a decay to pretty much any "hive power" operation (proxy, witness vote, proposal vote, delegation etc)
    • Sounds reasonable. I'm hoping for a sufficently long time period, e.g. 12 months + 6 months linear decay, or 18 months with no decay, because I can't imagine anything more tiring than being confronted with witness vote campagins every few months.
  • Reducing the number of daily votes
    • Great idea. Those 0.01% votes don't do much for most. Except for some extremely large whale accounts. Those will be forced to delegate to alts in order to not blow up rewards with every vote. Unless the number of votes is relative to account size - which adds more complexity to Hive. Or SMTs happened before and votes are decoupled from HP.
      Needs more discussion.

Vote for my witness: @blue-witness
H2
H3
H4
3 columns
2 columns
1 column
7 Comments
Ecency