VeriHash desires to get further involved in the Stakewise ecosystem through the running of a oracle node for the stakewise platform. A diverse set of oracle node operators helps ensure platform availability and resiliency against oracle failure.
The oracle will be hosted with the same HA infrastructure deployment that Verihash intends to provide for validation services.
However, to isolate concerns between oracle and validation operations the compute layers will be isolated at the node level and the validators will be namespace isolated at the cluster level.
The only shared services, which are accessed via internal cluster network calls will be the the execution (eth1) and consensus (eth2) layer clients.
The infrastructure is setup as follows:
HA Execution Layer clients targeting non-super majority client mix
HA Beacon layer clients targeting non-super majority client mix
Resilient compute layer for oracle workload hosting
OS and cluster level patching is automated
No SSH deployed, bastion only access to cluster nodes
2FA enforcement on remote access and cloud accounts
Elastic CPU, MEM, Storage to accommodate growth needs for oracles over time
VeriHash intends to provide oracle services for the present ethereum mainnet and gnosis mainnet chains.
VeriHash proposes the following specification be executed to modify the oracle contract in order to add VeriHash to the list authorized oracles allowed to submit votes for distributor, total reward and validators.
- DAO calls addOracle function of Oracle contract with the following parameter:
- account: 0xE11E57383312BE71B0589e1a3529FeC2A524975C
A poll is being done here first to gauge community support before calling for a snapshot vote.
As always, we invite StakeWise DAO members to share thoughts & comment on the proposal.