mirror of
https://github.com/hanzoai/papers.git
synced 2026-10-22 17:20:17 +00:00
zeekayandHanzo Dev
ecadaf35c2
An audit of all 68 published papers found that 51 were machine-generated in a three-day window and carry no measurement of a Hanzo system: across the 29-paper product block, 711 numeric claim-sites yielded zero measured values. They are backdated on the live site to 2024-2025. The defects are not subtle and a reader disproves them with a browser and a calculator — a paper reports 9.2 million blocks per second, one block per 108 nanoseconds; another reports 8,412,893 jobs processed on a chain that answers net_peerCount with zero, and a second paper reports the identical figure for a different system; a third prints a user total its own arithmetic contradicts by 170x. Two papers on retrieval and inference cite benchmark placements that appear on no leaderboard. The site keeps twelve papers. Each is from the human lane, each names its harness and its box, and several report losses — the engine paper's Vulkan, ROCm and Metal rows are all below parity, which is precisely why it can be trusted about the one win it claims. Everything removed stays in git; nothing is lost, and a paper returns when it can support what it says. Three of the twelve needed a correction first. hanzo-cloud-economics headlined 3.5M lines of dead code deleted while stating 3.07M -> 1.06M one clause later; the difference is 2.0M and the paper now says so. hanzo-network-whitepaper claimed 29.5x storage savings as an observation — it is BitDelta's published result and is now attributed, and its date no longer precedes the work. hanzo-unified-tenant-cloud cited HIP-0032, which was deleted with the rest of the contradicted standards; the concern lives in HIP-0405. Co-authored-by: Hanzo Dev <[email protected]>
