Fair on one point: section 5 walks through a single node role and never names a separate validator class. But section 8 already split them for you: "It is possible to verify payments without running a full network node." The paper accepted that most participants would carry headers and trust the longest chain rather than validate it themselves. That is the separation you say was never there, just not given a label. Where I would push harder is the word accessible. The person hashing at a party is not signing the block, the pool is. Three pools signed 67 percent of the last 130 blocks (mempool.space, 24h reading this morning): Foundry, AntPool, F2Pool. A thousand people hashing on one afternoon do not move that number by a single block. It makes mining tangible, which is worth something real, but tangible is not distributed. So I would keep both claims apart. A block party keeps mining visible and keeps the lottery ticket in people's hands, and the vote still costs energy, that part survived the whitepaper and the ASICs both. Whether that energy lands in one pool or in many is the question the party does not answer.