Hi Soph. Did you manage to acquire a list of validators with multiple servers / key?
1 Like
Yes we do. I will make an announcement today/tomorrow with the list of validator with backup node which we are going to request to remove from the network.
2 Likes
Perfect, thank you team 
I will obviously be on that list but I’m ready to go whenever needed 
3 Likes
Hello everyone,
Below is a list of validators with a backup nodes:
| Name | Address |
|---|---|
| RoboValidator_minimum fees | one1x8fhymx4xsygy4dju9ea9vhs3vqg0u3ht0nz74 |
| Moto Trust - Always Lowest Comission | one1c4w9danpa5v9zqurnl07lkqdcwyn3yfm86anqu |
| JungleCity | one13jewk8w7jah3r9jfahh8rlzpr5r6valascd0mn |
 Mintbes |
one12jell2lqaesqcye4qdp9cx8tzks4pega465r3k |
| HarmonyHUB | one1leh5rmuclw5u68gw07d86kqxjd69zuny3h23c3 |
| babylonodeONE | one14xkvsj8gnwl2tnu9wahfru35x8ppveaqdx5cnf |
| Smart Stake - harmony.smartstake.io & HarmonyAnalyticsBot | one1qk7mp94ydftmq4ag8xn6y80876vc28q7s9kpp7 |
| Solitaire | one1r3kwetfy3ekfah75qaedwlc72npqm2gkayn6ue |
| SoftNode | one16knqzazp2kxra3zx4sw32capqt3esg55wjg7ff |
 KysenPool Dragon  |
one1ctwewx0pmg8k0tc8vnx4guyq9jm7dwz5k98tlm |
Chickens Validator Original Testnet Dev  |
one18ky073zdrrmme3fs7h63wyzguuj6a3uukuc3gk |
| Validator.ONE Top Trusted Validator Low Minimum Fee | one14l4lst4qnm9fecv38450upfjym00s4ejz9mgdc |
| BBIT | one1wrvlznh27fywscexnc2l9fxk5gjelcqdnw8pvw |
| InfStones | one1l0wwv67lfelxhjvu6dkm9t8j5gsxev44lm6s02 |
| GGA | one1t3tex27l80cs4eltq5t7wymcxwwct6xxuyf7w4 |
| Guarda Wallet | one1qfpt5y3kuw8dnsd2d4lgjjzf849mfdzaxzum88 |
| Fortune – Highest Delegator Count Min Fee 34m Rewards Auto Shard | one1v0n7nw6c4fe88xnuasr0d65luult0fvclvvxmf |
| TokenNuggets | one1j34kvpa66hzqmf4ywa2cyhwn4se2a03lvhxv4n |
ONE4All - Community Validator  |
one13hr88u4zjrx2rf9gkdchawppdnsrctunlxug56 |
DK Validator - Secure Independent Staking  |
one1w7nvheulzwprf9d9a3r8sqtv5q47qlqx7kured |
| Staking Club | one1xthdv58tg7fc2qv7ltu6399hnvwtvcld9krzrx |
| Tec Viva | one18qk5uszfjq5wrkm2gfstqpx56jdpn0xd4563tk |
 Hank The Crank:gear: |
one139wxucm2rl0aag8ej24r2rh0qk86dylvszxg5u |
| AzureONE | one14v636te9jxp4d9f2c5uwa9hvqmmmut4fdtpxw5 |
| ONECelestial Validator | one1twcvkx63304dplxcmx0j9jm32u6er3k0hxuf7z |
| PeaceLoveHarmony.ONE | one1mlkylwnsgsam8cdxzn05hal3ytjngsunlpmp2j |
| TillyONE | one102lcjqy44ett8wu07dxdtce6gm988j0eu3z6cy |
| Legion - the ONE who is many High Self Stake Highest Uptime | one1r2lx24n0fpfch7cqyhccekqfd6dk79f0wqw7p4 |
| OneBullValidator | one1zcw3fua99t9te03mu6f5nne80p3rapfsxf2ur8 |
| Affinity Shard Top Trusted Community Validator | one1pzgc08u8xxj92srcgqutjkt6mmt6j8278zfpsk |
| Husaria ONE Validator | one1xrtkrcpx7edw40zxpp26up939gc68u8hwepvnx |
| Infinity Tech | one1slf58d4kaus4h9st228dxagqcv5afluwzuj0nd |
| Kiln | one149j0j8jx4mrjzzlnh299hmrd3rzr8ptyhksht9 |
Let me know if you have any questions
5 Likes
The only ones I havn’t seen contacts for on either: vstats, discord etc are:
- Kiln
- Infinity Tech
- Guarda Wallet
- InfStones
- SoftNode
- Solitaire
- Moto Trust
Does the team have contacts with any of these?
1 Like
I’d love to know more about justification behind blacklist, and yeah, I remember HIP17 voted it down. It’s antithetical to decentralized, permissionless blockchain.
Also, yes, we have active backup node now. Knowing if the IsBackup flag is working would be helpful. And, we’ve not seen a definitive “don’t do that message”. Maybe we missed, but it seems to be “at some point you won’t be able to do that”.
1 Like
Guarda, infstone, I have. For the other i believe at one point, we could talk to them in discord / telegram
1 Like
Hey, when we hit the pending delegation bug, we voted as a team whether we wanted to use that feature or not. We voted to use it thinking about how we could have prevented more damage if we actually used it during the hack. We and I completely forgot about HIP17. Going forward, and with leader rotation, considering HIP17, we can simply say that it will be practically impossible to use that feature.
It’s in our TO DOs
Yes, please don’t run backup node, it’s been a while it is in our doc : Requirements - Harmony but with leader rotation coming soon, we need to make sure we don’t have any.
1 Like
It could be a good idea to have a publicly available plan for the event of double signing and a fork in the chain. Eg exactly what a validator(s) must do to rectify. @sophoah
3 Likes
All set to go now, I dropped the backup a few days ago👍
Hey, let me try to draft an explanation here, and then we can decide if it’s clear enough to share publicly.
Essentially, a network fork occurs when validators on the network are out of sync and can’t agree on the latest leader proposal. This situation might arise when two leaders are active simultaneously, leading to a disagreement on block height and hash.
In this scenario, more than 33.33% of the validator network might have block X with one hash, while the rest have a different one.
To resolve this, the minority of validators can revert their block and sync to the correct one. Alternatively, all validators can revert block X and redo the consensus round
Thank you for the explanation. I more meant a step by step guide, a plan of action or flow chart. Something that when the network is stuck or a validator stuck, that we can follow to fix promptly ( with commands to run ).
Or do you think it’s more something that we alert the harmony team and a plan is created at that point?
1 Like
@sophoah Solitaire backup node will be taken down. You’ll also get contact details for solitaire on discord.
Is there a way to run a second node without signing, so that if the main node fails, the backup node can be manually enabled to be signing, with a current block DB? Would just removing all BLS keys do the trick, or confuse the backup validator node even more?
isBackup does sound like a great answer to this question.
Resolved this by using a dummy BLS key, as David proposed.
2 Likes
One example of a network outage is what happened 2 years back : Discord with the doc : Revert Beacon Chain Blocks - Google Docs
we did the analysis before and came up with the solution.
I’ll try to come up with a flow chart or a list of things to do/check (without the how in detail first then we can look at the how later on)
1 Like
Hello everyone,
Adding here for transparency and open communication what was shared in the validator telegram group : Telegram
My impression from the reaction from validator so far was that there is no concern for us to proceed with the 1% and I’d like to suggest a 2 internal slots per shard for this. (ie we will run 2 node with 1 bls key each to support the DNS node function)
Let me know if there are any concern
I putting here a poll as well to understand if the community is ok with the 1% harmony internal voting power with 2 slots.
I would still go with a HIP32 proposal that contains a full externalization, but the 0% would be achieve with two different HF:
- HF for leader rotation with internal node with 1% voting power and 2 slots per shard
- later on (once streamsync is operational) HF to remove the 1% and 2 slot per shard
Let me know what you think
- Yes, let’s go with 1% and 2 slot per shard first, then 0% later
- No, let’s go directly with 0%
0
voters
thank you everyone
1 Like
Going straight to decentralization is my vote. It’s time for every validator to be equal and follow the same steps as anyone else.
1 Like
I think the community should take over this role. Complete decentralization is needed. There are plenty of community members that could take on this function and, in return, will be a more desirable staking option.
2 Likes
Can you give any more information about what is actually required to run this role from a validator ? Pros, cons, benefits ?
Are we talking weeks, months until stream sync is available ?
2 Likes
HIP32 snapshot has been posted : Snapshot
Vote starts 5th March 14PM UTC and will end in two weeks 19th March 14PM UTC.
1 Like