First of all, I want to thank the community for providing their feedback on my post yesterday regarding the KE Score and how I used my own account as a case study. I was pleasantly surprised to see that there are still people genuinely interested in discussing this topic, which encouraged me to make a follow-up post.
In this post, I also want to share my intent to revive my KE Score and introduce the tools I’ve developed to help me visualize or simulate potential outcomes.
I'm quite excited about this, especially since I put considerable thought into the process and was able to create something I now call the KE Score Simulator.
But before I dive into that, I’d like to give a quick recap of the feedback I received on my previous post.
It turns out that my post helped demystify the KE calculation and sparked a healthy debate in the comments about the fairness, practicality, and limitations of this metric.
One particular comment stood out: a user shared how they’ve been rebuilding their KE Score through regular participation in the monthly HPUD (Hive Power Up Day). They reported a modest improvement from 1.81 down to 1.80. While that may seem like a small change, it’s still meaningful progress. After all, progress is progress. Things don’t have to be rushed; steady, consistent power-ups can lead to significant results over time.
Some users view the KE Score as a helpful guide for content curation. However, others argue that it shouldn’t be the sole factor in determining whether a blog post deserves support. Several commenters emphasized that curators should also consider the quality of the content and the intent of the author, rather than relying solely on raw numbers.
This point really highlights an important aspect of the Hive platform. We are all human, and we can’t reduce a person’s value to a number.
created using Sora
As a case study, I used data from Hivestats and projected those values to remain consistent over a span of four weeks. I also considered stopping the power down and participating in the monthly HPUD by powering up 200 Hive.
Curious about the potential outcome after a month, I enlisted the help of AI to assist in calculating the resulting KE Score. Surprisingly, even with these minor changes, the projected KE Score already looks much better than my current one. So cool!
Simulation Recap: The Case of @curamax
@curamax's baseline data:
- Author Rewards: 32,204.44 HP
- Curation Rewards: 10,848.13 HP
- Total Rewards (R): 43,052.57 HP
- Held HP (H): 7,060.13
- Current KE: 6.10
Goal: To lower down the current KE Score through planned actions:
- No power‑downs
- One 200 HP power‑up at the end of week 4 (HPUD participation)
KE Score Projection After 4 Weeks (No Weekly Power‑Down)
Baseline (week 0):
- Lifetime rewards R₀ = 43,052.57 HP
- Held HP H₀ = 7,060.127 HP
- Current KE = R₀ ÷ H₀ ≈ 6.10
Earnings pace (author + curation):
- 724.69 HP/month + 615.01 HP/month = 1,339.70 HP/month
- ⇒ 1,339.70 ÷ 4 ≈ 334.93 HP/week
Actions:
- No power‑downs
- One 200 HP power‑up at the end of week 4
1. Total Rewards After 4 Weeks
R₄ = R₀ + 4 × (HP/week)
= 43,052.57 + 4 × 334.93
= 43,052.57 + 1,339.72
= 44,392.29 HP
2. Held HP After 4 Weeks
H₄ = H₀
- (4 × 334.93) ← HP earned (author + curation)
- 200 ← one‑time power‑up at wk 4
= 7,060.127
1,339.72
200
= 8,599.847 HP
3. Resulting KE Score
KE₄ = R₄ ÷ H₄
= 44,392.29 ÷ 8,599.847
≈ 5.16 (potential KE Score after a month)
That would mean a reduction of 1.0 for every month! If done consistently, I may be able to achieve KE 1.0 in a span of approximately 6-7 months.
💡 Community Insight: What KE Is Considered Acceptable?
There is no "official" standard, but based on posts and curator discussions:
KE Score Range | Community Sentiment |
---|---|
≤ 1.0 | Excellent. Strong reinvestment. |
1.0 – 3.0 | Acceptable. Balanced participation. |
> 3.0 | Caution zone. Seen as draining value. |
> 5.0 | Red flag. Likely to miss out on big upvotes. |
Curators don’t judge only by KE, but many use it as one signal in their decisions.
✅ KE Score Improvement Tips
- Convert HBD to HIVE every payout and power it up
- Minimize or pause power-downs when possible
- Avoid sending out staked HP unless necessary
- Slowly add more HP over time through buys or payout earnings
Final Thoughts
Over the past few days of researching the KE Score, I’ve gained insights into how our staking actions can influence how we are perceived on the platform. Although this metric isn’t embedded in the Hive blockchain protocol, it has become a guiding reference for community curation.
That being said, I encourage curators to also consider the author's contribution to the platform by evaluating the quality of the content they produce. It’s equally important to recognize the human aspect of the platform, rather than relying solely on simplified metrics like the KE Score.
Every power-up you make shows your belief in the Hive ecosystem.
Start planning. Start staking. And start growing your influence.
Thanks for reading!
Join the CryptoCompany Campaign here: