im so fucking early on this narrative and willing to have a public discourse with anyone on this decentralized ai is the one space in crypto ive noticed that people think exists, but does not yet exist. where every project is either not tokenized yet or not on mainnet yet, and still in the development phase in both, it's that early it may be one of the most misunderstood sectors in web3. everyone is willing to believe and say anything that will pump their bags. we as humans are very simple, incentivization is everything when it comes to belief. once projects like @hyper_tensor @PrimeIntellect @gensynai @thewebAI (if they tokenize) @exolabs (if they tokenize) come out, (there may be more, if so, let me know) all of these AI projects that dare to use the terms like "decentralized", "p2p", etc. people will then finally understand what decentralized AI is supposed to look like make sure to give me credit in a few years when this is standard in this sector, because it will be

first ever overwatch reveal, testing

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

wait how do u have a commit-reveal scheme in a $TENSOR subnet if they aren't blockchains? glad you asked... each subnet utilizes a database authorizer base that enables an array of validators, including the PredicateValidator. This enables the nodes to validate stored values