Are these leader nodes subjected to slashing?
1 Like
Shard 1
BLS: 1015d0a7cb7c1a6270a0f9896cee51f5765828e7baad827f37b7e641682c484cbc0633edb6e7257b26ea8c1e3016ce05
Forgot to put our key before if no specified shard is necessary
Shard2: 0913f428a2af63e8428d314b80f65aaf477b66fd382b0b6cf3b8cee3562b8d93cf51198aece70e1e5a808b8dbb299906
and again our node:
Happy to do this on Shard 1, I’m not currently consistently elected though. Definitely would prefer to have the passive redundant node mentioned above implemented along with this. Foundational stake/funding would be helpful as well.
Shard 1: bbe4f7d298fbd528f7631ccefc66d49cf0e75eceb94bd6a4a967ff8342480ea27eba38ee6f118a52f2dff17bfe3af505
Validator Page:
1 Like
1 Like
second server running at the same time is not recommended. you may use the secondary server as a backup, but not run at the same time. It is strictly forbidden by any PoS blockchain.
3 Likes
appreciate everyone for your help to be the external leaders. I’ll make some summary and come up with a staged plan. thanks a lot. love the ONE family.
8 Likes
Thank you for replying Leo 
I apologize for the delay. I somehow did not notice that you replied to me until now.
I currently have both nodes signing on the same BLS key on shard 1 per the redundant node setup docs. Perhaps once I have enough Harmony delegated to StakeIt.ONE I can run a shard 0 key on the second node. Perhaps I should change the isbackup=false in the harmony.conf to isbackup=true on my 2nd node to be on the safe side?
btw I this family too!
I’ll put my BLS key & staking dashboard profile here just you still need a volunteer on shard 2:
d17cdf35937386b35d6130638883c1f08131ce0a53ddb14e784f7ed8b6daa50c0d231ecc533fee33a0225781d59b778a
VietStaking
we are not going to implement the allow list feature for now as @rongjian had commented in the design/plan doc. https://www.notion.so/harmonyone/allowlist-of-external-leaders-73d4fba057904b27b4055333c57a4d22
Rather, we will look into the leader rotation implementation at first, and allowlist later. Thanks everyone for your interest and support. We will come back later for the allowlist.
5 Likes
I can’t access the doc. But thanks for the follow up.
1 Like
Same here. I tried logging in with StakeIt.ONE’s Gmail account and it says that I don’t have permission to view it and to contact the author for permission. It seems that they have not made the document viewable by the public. If they change access permissions on the document we should be able to view it.
1 Like
@leo I have marked this as ON HOLD - please can you update the original post with the explanation? Thanks
4 Likes
hey guys, i know this is on hold but pops team validator would also like to participate in this when its relaunched!
4 Likes
The doc should be accessible by public now.
4 Likes
Thank you, Leo! Have a good day!
I can be a leader on any shard, I think it should be a requirement that leaders also open their RPC publicly and are inserted in a load balanced RPC service to help bootstrap the environment with equipped RPC endpoints
2 Likes
Good info, I would put myself up for a leader on s0. Currently use 2 keys: 227ae3b3b586acd95b59f323d189529d37ea5caf84eef33a6403062a699c5f3b10e47e56f7a2b7a1b2d3555917114d80
48ecc2cec115a4bce321f8f05aab040926f9f32c1db4a2beb6631db56ffa15dc0044381308e8c2b4e823db29af65ce18
I am running a bare metal server + cloud backup, both able of running s0. Are there any plans to provide leaders with some incentive? One could be a guaranteed stake of some determined amount of ONE to help secure election?
1 Like
Hi, this HIP is being implemented, [consensus] HIP-18: Allowlist for external leaders by peekpi · Pull Request #4146 · harmony-one/harmony · GitHub
1 Like
Requirement of the validators in the allowlist.
- powerful node to run as the leader. dedicated 36 core CPU, 72G ram, SSD/Nvme, 10G+ network bandwidth, specification please refer to c5.9xlarge (Amazon EC2 C5 Instances — Amazon Web Services (AWS))
- no hot backup node, only one node running. if you run two nodes, there will be hardfork and will get slashed. You may use the hot stand-by node mode.