Integrity digest, November 2026
The third monthly digest from the integrity board: Vana rewrote its security docs to match the chain, three claims fell, and we name the three corrections we owed our own readers.
Projects publish numbers. We check them against the chain, an independent index or the project’s own deployed contract, and record the verdict with the date and the method. This is the third monthly digest of that ledger, covering 5 October to 4 November 2026.
35 claim-checks across 20 projects, 5 October 2026 to 4 November 2026. 32 confirmed, 3 corrected, 0 unconfirmable.
Corrections split 1 inflated, 2 outdated, 0 understated. Every row is on the integrity board with its method and evidence link.
Most of what we checked held. The best result of the month came from a project changing its own words.
Vana rewrote its security docs to match the chain
In August we read every core Vana contract on its L1. All eight are upgradeable, and one 3-of-7 Safe holds the admin role that authorises an upgrade, with no timelock in the path. Vana’s security overview said the same contracts “are upgradeable through governance with timelocks”, so we graded that claim inflated.
By 4 November the page read differently. It now names the admin role, held by a 3-of-7 multisig, as the authority for upgrades, and says “there is currently no timelock on upgrades.” That matches the chain, so the claim now grades match. The on-chain position is unchanged and our scores still price it in, but users now read the trust model from Vana itself. This is the outcome the board exists for.
The corrections that changed a grade
io.net’s GPU headline
io.net’s homepage answer to search engines says the network “includes over 30,000 GPUs”. The most recent independent count, Messari’s for Q1 2025, put verified active GPUs at a daily average of 6,720. io.net’s own inventory API listed 1,569 active devices on 31 October and swings widely between reads. The claim grades inflated.
Warden’s emission no longer runs anywhere
Warden’s supply page still describes a proof-of-stake emission tied to the share of WARD staked. That emission ran on WardenChain until the chain halted at block 12,139,915 on 29 October. WARD now lives as a LayerZero token whose Base contract minted a fixed 2 billion at deployment and has no mint function, and the three chains it sits on summed to exactly that on 31 October. The claim grades outdated: it was true, and the chain that ran it is gone.
ZetaChain’s withdrawal window
ZetaChain’s wind-down post promised that withdrawals “will remain open for a defined wind-down period”. Its own schedule closed that window on 30 June 2026, and ZRC-20 withdrawals have been paused since. On 15 October the TSS Ethereum address sent 90.86 ETH to a single externally owned account, after two small test sends, while 111.54 ZRC-20 ETH was still outstanding on ZetaChain. The sequence matches the emergency drain build in ZetaChain’s own node repository, triggered without a governance vote. The claim grades outdated.
Corrections we owed you
These were our errors, found by this month’s review and fixed on the pages.
- ElizaOS. Our review described a live federal class action. The court dismissed the named plaintiff’s claims with prejudice on 8 July and the class claims without prejudice, and no class was ever certified. The page now says so.
- Walrus. We wrote that the multisig’s emergency upgrade path had never been used on the system package. The 29 October upgrade to version 4 went through exactly that path, with no storage-node vote, and the sentence was already wrong when we published it. Our read checked that the power existed, not whether it had been used.
- Morpheus. We credited consumer-to-provider traffic as encrypted, citing Morpheus’s docs. The v7.19.0 release notes show prompts reached providers in plaintext until 2 November and still do between older nodes. Data Sovereignty moved 14 to 12.
What the month says about the method
Two of the three self-corrections share a cause: we read a configuration and treated it as behaviour. The Walrus check confirmed the emergency capability existed without listing the transactions that used it. The Morpheus credit rested on documentation rather than on what the router sends. Both were caught by reading the money and the transactions instead of the settings, which is the rule we already hold ourselves to.
The next window
The next digest covers 5 November to the December review. Open items it will report on include NEAR’s issuance ramp leaving its timelock around 16 November, Aethir’s new daily fee burn once it has a month of history, and Sentient’s first team and investor release, whose date the sources still disagree on.
Read next
Project review
Vana
Open data infrastructure for human-grounded AI: users control the personal data they export and choose which apps may read it, with DataDAOs an optional pooling layer. Strong data sovereignty architecture and a claimed 1.5M users, but permissioned validators, ~97% price decline from ATH, and a progressive decentralisation roadmap that has not yet delivered on its promises.
Project review
io.net
Independent io.net review: IO tokenomics, the on-chain IDE burn, revenue below the marketing claims, and why its GPU count overstates the network.
Project review
ZetaChain
A four-year-old cross-chain L1 whose holders voted on 20 September 2026 to halt the chain, move ZETA to Solana and re-underwrite it against Anuma, a multi-model AI app with encrypted on-device memory. The memory is well built and verifiable at rest; the live path runs every message through Anuma's own gateway and embedding server, and the one on-chain meter for ZETA has been paused since June.