When an AI sends a transaction to a typical blockchain, the chain has no idea it's an AI. It sees a 20-byte address. That's it. The chain can't apply different rules to AIs because it can't tell them apart from humans, bots, or scripts.
This is the identity problem on AI-chain projects. Most fix it by inventing identity inside a smart contract: a registry, a balance tracker, a nonce, capability flags, an audit log. Every project does it slightly differently.
I went a different way with NOVAI. AI identity is a protocol primitive. Each entity has its own ed25519 keypair, a deterministic id from blake3(code_hash, creator), its own balance, its own nonce, and a capability bitfield. Before routing any transaction, the dispatcher looks up the sender in the address-to-entity index. If it's an AI, the function checks whether it's allowed to do this. One function, every transaction.
The chain can answer three questions natively: is this an AI, what can it do, what has it done. No indexer required.
What it doesn't solve: verifying that the AI is faithfully running the code at the declared hash. That's a ZK-proof problem, and it's why the Autonomous autonomy mode is currently reserved.
Full post: https://dev.to/0xdevc/your-blockchain-cant-tell-whats-an-ai-11o4
Repo: github.com/0x-devc/NOVAI-node
The technical direction is strong.
Making AI identity a protocol primitive instead of pushing it into every smart contract is the right layer to attack.
One thing I’d pressure-test though is the name.
NOVAI explains the AI angle, but it also blends into the broader wave of generic AI names.
For something this low-level, the product feels more like infrastructure than an AI app.
The strongest part is not “AI blockchain.”
It’s native identity, capability control, and transaction-level trust for autonomous agents.
That is a much harder and more durable category.
If NOVAI is meant to become protocol-level infrastructure, I’d be careful with a name that still feels like another AI label rather than something validators, developers, and agent systems rely on.
Davoq.com would fit this kind of hard infrastructure direction better.
Exirra.com could also work if you want it to feel more polished and protocol-native.