Hypertensor Overwatch Node testing
Pretend you don't have TikTok brain rot and read all of the following, lots of good informatoin nuggets
What's happening here:
The setup here is 2 nodes hosting AI modelsโin a subnetโand 1 Overwatch Node verifying
There is 1 Onode that is verifying:
1. SUBNET IS DECENTRALIZED
- has publicly available bootnodes
- allows entry to access the DHT (distributed hash table)
- is running proof of stake
2. CONSENSUS ACCURACY
- ensure nodes registered (and in consensus) on-chain are also in the subnets DHT, AKA making sure they are actually in the subnet by pinging them. Think about it like this, you can right now go check if a node is running in Ethereum, what these Onodes do is ensure the nodes are running in the subnet since they're off-chain networks.
The Onode then scores its findings via the node algorithm and runs a commit-reveal scheme to the blockchain.
#2 is very important. It ensures no subnet developers are faking nodes, no nodes are faking getting rewards, and subnets aren't just letting nodes partake in consensus without them being IN the subnet.
Overwatch Nodes perform more tasks, such as ensuring a GH exists, verifying the template (sha-256 checker), benchmarking the subnet and nodes, etc.
Off topic:
When it comes to networks with off-chain sub-networks in a reputation-based consensus model, it's important to verify and standardize what happens off-chain. It's far too easy to fake being a node and copy those scores on-chain reputation, which can end up accounting for over half of the on-chain activity.... or more...
We have multiple mitigation tactics and layers in place to prevent these issues, which makes it improbable for them to occur on Hypertensor.
It will become a builder's paradise
Off topic 2.0:
Subnets have very little requirements, such as being decentralized with the utilization of a DHT, storing all nodes under the "node" key in the DHT records, utilizing PoS for subnet entry, and utilizing signature authorizers for all p2p communication