[SWIP-09] Onboard VeriHash as Node Operator in StakeWise with 250 keys on the Ethereum Network

Proposals
1

Summary

Name of the node operator: VeriHash Inc

Location of headquarters: Oregon/Washington USA

Network: Ethereum

Number of keys requested: 250 keys

Revenue share percentage requested: 50%

Motivation

We bring decades of experience architecting and administrating infrastructure in many deployment environments ranging from on-premises startups to multi-cloud Fortune 500 companies; and we excited to bring that experience here for the benefit of the stakewise platform.

Please see our testnet work for more information about us and our work prepping toward this proposal.

Our responses to the Node Operator Onboarding Questionnaire can be found here.

Specification

  • DAO calls addOperator function of PoolValidators contract with the following parameters:

    • operator: 0xE11E57383312BE71B0589e1a3529FeC2A524975C
    • depositDataMerkleRoot: 0x81cb61ee13adf99bca42ccb60556bdbc360dbc690737e64cd9ddd71f26e5688e
    • depositDataMerkleProofs: /ipfs/QmPSZhwqmCje4CCAtkGGQweqbTmw2NpAW2FrE7EA4fsvMs

  • DAO calls setOperator function of Roles contract with the following parameters:

    • account: 0xE11E57383312BE71B0589e1a3529FeC2A524975C
    • revenueShare: 5000

  • If the proposal will be approved, the operator must perform the following steps:

    • Call operator-cli sync-vault or operator-cli sync-local with the same mnemonic as used for generating the proposal
    • Create or update validators and make sure the new keys are added
    • Call commitOperator from the 0xE11E57383312BE71B0589e1a3529FeC2A524975C address

Vote

! Please make sure to examine the responses to the Node Operator Assessment Form before voting!

Should the StakeWise DAO onboard VeriHash Inc as Node Operator with 250 keys on the Ethereum network?

  • Yes

  • No

0 voters

Discussion

As always, we invite StakeWise DAO members as well as the members of the existing node operator set to share thoughts & comment on the proposal.

4 Likes
2

Hi Brandon! :slight_smile: (@bgraham-vh).

Would you be willing to clarify the poll question, replacing Y with “VeriHash Inc” and Z with the number of keys (I’m assuming 200 keys based on your subject line).

Also your title of the post indicates Ethereum network. However in the poll you are asking for Ethereum and Gnosis Chain network?

Thank you for helping to clarify my questions. :slight_smile:

3

Well shoot…the one thing my sed didn’t catch.

1 Like
4

It wont let me change it. It states that I can’t change the poll after 5 min. I suppose I can resubmit this with it changed unless admin can change.

it should Read

Should the StakeWise DAO onboard VeriHash as Node Operator with 200 keys on the Ethereum network?

5

i was able to delete the poll and re-add it though it cleared the votes :frowning:

Better to have it right.

1 Like
6

You’re doing great! I appreciate you taking the time to share your proposal on the forum! :slight_smile:

7

The fact that you use sed makes my day :smiley:

8

Note: We updated the proposal to 250 keys vs 200 based on feedback we received.

This cleared the voting again in order to update the poll title.

Apologies once again for the changes.

1 Like
9

Quick update here I am not sure if we said what clients we were intending on running in the survey or if they were our newly updated selections

So here they are:

Consensus: Lighthouse and Teku
Execution: Erigon and Nethermind (geth is presently syncing as well incase we need to use that due to errors in the erigon helm deployment at present)

1 Like
10

Erigon deployment issue resolved and now syncing. Geth removed from cluster.

11

Above the vote it says:

Where is the Node Operator Assessment Form?

1 Like
12

I believe the stakewise team attaches it to this post along with the video of the live demonstration we did as well.

I know they have been busy and we planned on pinging them about these items first thing next week.

1 Like
13

Live Demo is available in Google Drive: Part 1 and Part 2

2 Likes
14

Now everyone gets to see our silly mugs!

3 Likes
15

Cluster Status Update:
Nethermind, Synced
Erigon, 90% Synced
Lighthouse, Synced
Teku, 90% Synced
Vault, deployed and auto-unseal tested
Alerting tested and functioning as expected
Validators, PVCs created but validators offline until there are keys to sync

2 Likes
16

Verihash is now a hodler, albeit of a tiny amount, of SWISE. This is to facilitate participation in snapshot votes going forward and we intend to grow it over time.

2 Likes
17

Well done! Thanks for participating in the StakeWise DAO! :slight_smile:

18

Cluster upgraded to the latest stable client versions after testing on prater testnet. Most importantly this pulls in a fix for teku that was released yesterday to address a GC issue that can cause teku clients to fall out of sync

Vault: 1.9.2
Erigon: 2022.03.01
Nethermind: 1.12.6
Teku: 22.3.2
Lighthouse: 2.1.5
Validators – Lighthouse: 2.1.5

1 Like
19

It should be noted that even though we said we planned on operating nodes out of North America that is just our choice of Home region. We are capable of redeploying operation or standing up new operations across many different geographies if there are requirements to do so. In fact at present, we run clusters in both the US and EU.

1 Like
20

Cluster Sync Statue update:
Lighthouse - Synced
Teku - 200K slots away from synced
Erigon - 100K blocks from synced
Nethermind - Synced

1 Like