When I was still below the Top100 rank, it was quite depressing for me to see that my low ranking preventing me from appearing in the official witnesses page was partly due to the fact that Hivers were still casting votes for witnesses who are inactive.
## Goal Now that I have gone up to the Top80, the horizon looks much nicer. However, new witnesses are still struggling to let the world know they do exist, hence this post to get people to review their witness votes regularly.
The blockchain used to have a rule that automatically skip inactive witnesses that are still registered after 24 hours of inactivity. That meant that you could just turn off your witness and the blockchain would just ignore you after 24 hours. However, this logic has been recently removed and inactive witnesses who have not un-registered are still schedule for block production but will miss the block. The higher their ranking is, the more frequently they are scheduled and the more blocks will be missed slowing down the network.
Active low ranked Witnesses who might need your votes
First, lets give more visibility to witnesses that are ranked below #100 and are not displayed on the official witnesses page. Please learn about them and consider casting a vote for them if you believe they are worth it.
- Rank 101: @mintrawa is using v1.24.2. Produced 3h53m ago.
- Rank 103: @reazuliqbal is using v1.24.4. Produced 7h18m ago.
- Rank 105: @fernandosoder is using v1.24.4. Produced 1h45m ago.
- Rank 106: @jamzed is using v1.24.4. Produced 8h8m ago.
- Rank 107: @dmitrydao is using v1.24.4. Produced 7h33m ago.
- Rank 111: @lapingvino is using v1.24.4. Produced 38m ago.
- Rank 117: @lootkit.witness is using v1.24.6. Produced 13h45m ago.
- Rank 118: @hagie is using v1.24.2. Produced 11h29m ago.
- Rank 129: @veteranforcrypto is using v1.24.4. Produced 14h20m ago.
- Rank 130: @dpoll.witness is using v1.24.2. Produced 1h27m ago.
- Rank 134: @elindos is using v1.24.4. Produced 11h52m ago.
- Rank 142: @apshamilton is using v1.24.4. Produced 1d ago.
- Rank 151: @whiterosecoffee is using v1.24.7. Produced 19h52m ago.
- Rank 193: @pcste is using v1.24.4. Produced 2d ago.
List of inactive witnesses in the Top200
This is a list of retired, disabled and outdated witnesses that are so for over 4 consecutive weeks. You should consider removing your votes for them. The higher they are ranked, the more important it is to review your votes for them.
Retired Witnesses
The witnesses listed below are known to have retired and disabled their node. You can remove your witness vote for them.
- Rank 66: @c-squared was using v0.23.0. Inactive 114d ago.
- Rank 69: @nextgencrypto was using v0.23.0. Inactive 167d ago.
- Rank 85: @utopian-io has retired. Produced 591d ago.
- Rank 98: @furion is still using v0.20.5. Produced 485d ago.
- Rank 99: @teamsteem has retired. Produced 454d ago.
- Rank 100: @jerrybanfield has retired. Produced 693d ago.
- Rank 108: @wackou has retired. Produced 953d ago.
- Rank 116: @roadscape has retired. Produced 1139d ago.
- Rank 122: @arhag has retired. Produced 1181d ago.
- Rank 147: @fulltimegeek has retired. Produced 696d ago.
- Rank 171: @noblewitness has retired. Produced 535d ago.
- Rank 181: @demotruk has retired. Produced 662d ago.
- Rank 197: @rival has retired. Produced 734d ago.
Outdated Witnesses
The following witnesses are still active but have not updated their server to use a valid version of the blockchain. Depending on how long they have been disabled for, you can decide whether to keep or remove your witness vote for them.
- Rank 71: @delegate.lafona is still using v0.23.0. Produced 50d ago.
- Rank 75: @busy.witness is still using v0.22.2. Produced 266d ago.
- Rank 81: @blockbrothers is still using v0.22.1. Produced 248d ago.
- Rank 91: @steemgigs is still using v0.23.0. Produced 103d ago.
- Rank 93: @fyrst-witness is still using v0.22.1. Produced 248d ago.
- Rank 102: @coingecko is still using v0.22.1. Produced 248d ago.
- Rank 109: @adsactly-witness is still using v0.22.0. Produced 248d ago.
- Rank 110: @steemed is still using v0.20.10. Produced 454d ago.
- Rank 114: @partiko is still using v0.20.7. Produced 454d ago.
- Rank 120: @justyy is still using v0.22.1. Produced 248d ago.
- Rank 121: @battlegames is still using v0.23.0. Produced 40d ago.
- Rank 128: @yehey is still using v0.23.0. Produced 40d ago.
- Rank 135: @bue is still using v0.22.1. Produced 249d ago.
- Rank 145: @steemwisdom is still using v0.20.5. Produced 774d ago.
- Rank 146: @steemhunt is still using v0.22.5. Produced 248d ago.
- Rank 150: @yoodoo is still using v0.22.0. Produced 323d ago.
- Rank 161: @cryptopassion is still using v0.22.1. Produced 275d ago.
- Rank 164: @swisswitness is still using v0.22.1. Produced 294d ago.
- Rank 166: @chainsquad.com is still using v0.19.12. Produced 790d ago.
- Rank 167: @masteryoda is still using v0.20.5. Produced 768d ago.
- Rank 169: @ro-witness is still using v0.22.0. Produced 249d ago.
- Rank 170: @steem-bounty is still using v0.20.6. Produced 538d ago.
- Rank 173: @boatymcboatface is still using v0.20.10. Produced 544d ago.
- Rank 174: @bukio is still using v0.22.1. Produced 249d ago.
- Rank 175: @we-the-people is still using v0.23.0. Produced 81d ago.
- Rank 177: @puncakbukit is still using v0.23.0. Produced 55d ago.
- Rank 179: @birdinc is still using v0.23.0. Produced 203d ago.
- Rank 184: @gridcoin.science is still using v0.22.1. Produced 250d ago.
- Rank 185: @triple.aaa is still using v0.22.5. Produced 248d ago.
- Rank 188: @provenezuela is still using v0.20.9. Produced 455d ago.
- Rank 194: @ety001 is still using v0.22.5. Produced 248d ago.
- Rank 195: @pjau is still using v0.20.10. Produced 454d ago.
- Rank 196: @bobdos is still using v0.22.0. Produced 305d ago.
- Rank 198: @snackplus is still using v0.20.10. Produced 561d ago.
Disabled Witnesses
The witnesses listed below have disabled their node. Depending on how long they have been disabled for, you can decide whether to keep or remove your witness vote for them.
- Rank 73: @reggaemuffin was using v0.22.0. Inactive 348d ago.
- Rank 74: @clayop was using v0.22.0. Inactive 274d ago.
- Rank 78: @xeldal was using v0.22.1. Inactive 344d ago.
- Rank 90: @ihashfury was using v0.23.0. Inactive 112d ago.
- Rank 104: @dsound was using v0.23.0. Inactive 67d ago.
- Rank 112: @chitty was using v0.23.0. Inactive 70d ago.
- Rank 113: @wise-team was using v0.23.0. Inactive 240d ago.
- Rank 115: @charlieshrem was using v0.20.10. Inactive 454d ago.
- Rank 119: @danielsaori was using v0.22.2. Inactive 266d ago.
- Rank 123: @lux-witness was using v0.23.0. Inactive 233d ago.
- Rank 124: @steempty was using v0.19.2. Inactive 988d ago.
- Rank 125: @witness.svk was using v0.19.0. Inactive 1135d ago.
- Rank 126: @prc was using v0.23.0. Inactive 67d ago.
- Rank 127: @kushed was using v0.19.2. Inactive 979d ago.
- Rank 131: @oracle-d was using v0.22.0. Inactive 414d ago.
- Rank 132: @blockchained was using v0.20.8. Inactive 691d ago.
- Rank 133: @helpie was using v0.22.1. Inactive 300d ago.
- Rank 136: @krnel was using v0.20.10. Inactive 511d ago.
- Rank 137: @joseph was using v0.20.7. Inactive 709d ago.
- Rank 139: @blueorgy was using v0.19.2. Inactive 999d ago.
- Rank 140: @au1nethyb1 was using v0.19.2. Inactive 974d ago.
- Rank 141: @datasecuritynode was using v0.19.1. Inactive 1064d ago.
- Rank 143: @bitcoiner was using v0.19.2. Inactive 1020d ago.
- Rank 144: @steemcommunity was using v0.20.8. Inactive 574d ago.
- Rank 148: @liberosist was using v0.20.10. Inactive 454d ago.
- Rank 149: @theprophet0 was using v0.19.1. Inactive 1021d ago.
- Rank 153: @bitrocker2020 was using v0.22.0. Inactive 406d ago.
- Rank 154: @thekitchenfairy was using v0.22.0. Inactive 259d ago.
- Rank 155: @cyrano.witness was using v0.19.0. Inactive 1222d ago.
- Rank 156: @bitcube was using v0.13.0. Inactive 1525d ago.
- Rank 157: @ayogom was using v0.22.0. Inactive 447d ago.
- Rank 158: @tdv.witness was using v0.16.0. Inactive 1428d ago.
- Rank 159: @davinci.witness was using v0.20.9. Inactive 478d ago.
- Rank 160: @steem-id was using v0.19.2. Inactive 1053d ago.
- Rank 162: @felixxx was using v0.20.6. Inactive 699d ago.
- Rank 163: @steve-walschot was using v0.14.2. Inactive 1489d ago.
- Rank 165: @nonlinearone was using v0.16.0. Inactive 1374d ago.
- Rank 168: @sc-steemit was using v0.20.5. Inactive 662d ago.
- Rank 172: @travelfeed was using v0.22.1. Inactive 250d ago.
- Rank 176: @moisesmcardona was using v0.19.4. Inactive 875d ago.
- Rank 178: @asbear was using v0.19.6. Inactive 798d ago.
- Rank 180: @chbartist was using v0.22.1. Inactive 389d ago.
- Rank 182: @markangeltrueman was using v0.20.6. Inactive 750d ago.
- Rank 183: @jrswab was using v0.20.5. Inactive 733d ago.
- Rank 186: @untersatz was using v0.22.2. Inactive 266d ago.
- Rank 187: @yuriks2000 was using v0.20.10. Inactive 502d ago.
- Rank 189: @steemitportugal was using v0.23.0. Inactive 68d ago.
- Rank 190: @koinbot was using v0.22.1. Inactive 281d ago.
- Rank 191: @agoric.systems was using v0.19.2. Inactive 1077d ago.
- Rank 192: @jatinhota was using v0.19.6. Inactive 824d ago.
- Rank 199: @bacchist was using v0.19.2. Inactive 1098d ago.
I can't understand this. Is there no way to automatically a witness' status if they stop producing blocks after a fixed period of time. After a longer period of time, they should have their votes cancelled!
This whole system seems ridiculous and prevents people from getting the exposure they deserve. Totally bizarre and I will go back to my list to audit and recast votes as necessary.
There are security issues when it comes to automating things around witness votes but yes, I'd like to see someone coming with better but safe idea.
As for exposure, I've submitted a code change for showing more witnesses on the witness page:
https://gitlab.syncad.com/hive/wallet/-/merge_requests/81
After missing a few conseutive blocks, a witness will be disabled by default.
Votes for dead witnesses is not a problem at all.
op is just fishing for witness votes.
That was how it was in the past but this rule does not apply anymore. Unless a witness disables its account by broadcasting they disabling key it is still scheduled for producing but will miss blocks.
You can see by yourself, on Fri 27th Nov 2020 01:31 AM Sydney Time, I took these screenshots:
As noticed, @busy.witness has not disabled the witness for 38 weeks now, however https://hivekings.com/witnesses does show that that witness has recently missed 3 blocks (see the
+3near the missed block count).Check that page again tomorrow and notice the number of missed blocks would have increased.
If you now check the witness schedule (https://hive.arcange.eu/schedule/) you will noticed that some witnesses who have missed blocks for a long time are still scheduled. For example, @delegate.lafona is still scheduled to produce a block despite having missed blocks for the last 7 weeks.
Having stopped your witness for almost two years now, you mustn't know that change of rule inside the blockchain code.
What update was that ? When did that happen ?
And: Why ?
I can't exactly remember when it happened but it was before the split STEEM/HIVE. The reason, not sure...
It seems, you are right...
@delegate.lafona has missed blocks since yesterday.
Is there a knowledgable witness, who knows, why this was changed ?
@delegate.lafona, last a_slot: 47,677,689
current head block: 49,030,085
from
get_witness_by_accountedit:
@ busy.witness: 41,435,907
Those are last produced block numbers not number of missed blocks
Paging and showing all witnesses will be helpful.
It's coming:
https://gitlab.syncad.com/hive/wallet/-/merge_requests/81
Thanks for the mention, for your great work to give more visibility and information about witnesses with your weekly report, for the low ranked witnesses with post like this one 👍
Witness FR - Gen X - Geek 🤓 Gamer 🎮 traveler ⛩️
Don't miss the Hive Power UP Day! more info here
So true and the ones that do what’s needed and do work need votes and exposure but casting witness votes still is something people need to do but lack. I will try to do another to ask for voting.
And I miss my blockbrothers time
The more users vote for Witnesses, the more secure will our network be.
I know but it’s a thing that has the least focus for new people , we do our best to change that in the terminal but we got our work cut out for us
But I still believe witness votes should expire a year after being cast/renewed.
Vote expiration is planned for HF25.
This is excellent news. We can see members actively voting for their witnesses.
My node is running again. Worked the last weeks on the infrastructure after my system showed some serious weaknesses at the last HF.
Welcome back
Confirmed that you are producing again and I've removed you from the post above
The ranking will not change drastically if vote decay is not implemented. For the last year or so, top20 HIVE witnessess are all the same.
Edited.
I saw @blocktrades post above, "Vote expiration is planned for HF25".
Although the Top20 has been stable (ish) we've seen quite a bit of movement with some witnesses dropping off and others like @stoodkev (congrats btw) jumping in. Just like with any automated stuffs, it needs to be implemented carefully. Educating users and a regular reminder to review their votes still needs to be done or else with vote decay, if users don't re-cast their votes, we'll have some issues.
Thanks man!
You definitely deserve to be in the top20, hope you make it soon! =)
Thank you for showing me here. I am currently struggling to be among the Top100
I published several times a couple suggestions for the Witness eternal vote problem. Here is one of them which happens to also be my witness topic.
https://peakd.com/hive/@fernandosoder/important-things-to-be-considered-regarding-vulnerabilities-on-hive-blockchain
I also for a couple times created topics mentioning all voters of disabled witnesses to call for their attention. You can check them in my profile.
Thanks for this excellent post pointing out all the dead witnesses that are taking votes from live witnesses like myself.
Please, everyone who reads this - review your witness votes and consider a vote for me @apshamilton and other excellent witnesses like @elindos, @fernandsoder and the other's listed above.
@quochuy, consider a witness vote for a fellow Aussie, who actually knows where Wyoming, NSW is. :-)
@jpbliberty has given @quochuy a witness vote on behalf of itself and @apshamilton.
Keep up the good work in highlighting dead witnesses.
The more votes for dead witnesses, the more yours count.
The more votes for dead witnesses above new witnesses, the more difficult it will be for the new witnesses to raise in rank. And since the blockchain does not disable witnesses that misses blocks for a long time anymore, it's also affecting the network. See my answer to your other comment.
Thanks for the witness vote.
I really try to keep on top of this and will recheck tonight. Would there be anyway to have an alert system that notified the user if their witness votes need a refresh.?
Posted using Dapplr
Thanks for the reminder! I thought I had a vote to assign the other day and when I went to my list of witness votes saw I still had votes for inactive witnesses. I must analyze it further to make sure they are current. Everyone should reblog this as a reminder, I will. !tan
Congratulations, @industriousliv You Successfully Trended The Post Shared By @quochuy.
You Utilized 1/3 Daily Summon Bot Calls.
TAN Current Market Price : 0.900 HIVE
I'm considering re-activating my witness after I build a machine that can run HIVED long-term.
Would you happen to know how much HD space it currently uses?
My server has 32GB RAM and 500GB SSD.
Congratulations @quochuy, You Earned 0.248 TAN & Curators Made 0.173 TAN.
Join CORE / VAULT Token Discord Channel or Trade TANGENT Token
TAN Current Market Price : 1.940 HIVE
Why not do your blog in Spanish aswell I think there are some votes for you there
I did my post hope it helped
Hi, I don't speak/write spanish and if I have to use a translation app then I guess users can also translate the article themselves using the browser translation feature. Additionally, if I start with Spanish, other languages might request for a translation too :-D
You are the one wanting votes 😉 with a simple translation of this blog you might gain the amount to get you in the place where your want to be stating in the beginning of this blog
Thank you hehe.
My goal has already been reached a while ago. The reason I created this post is not for myself but for the new witnesses and to raise attention on inactive witnesses who are still receiving votes and might be hurting the network.
Maybe they need to do this kind of blog aswell and show their excistance
cool!
helped more than just one!
🙏🙏🙏
Cool
thank you for upvoting my last post man :)
Downvoted for intentional misinformation
Thank you for participating to post curation
Thank you