Geth Pruning Benchmarks and Quiet API Tradeoffs
Two pull requests against the geth repository closed in the same window today. One was a parallel state pruning experiment that ran into a database wall. The other was a defensive limit on a rarely used HTTP API that maintainers decided was not worth the maintenance load. Together they show how Ethereum execution client decisions actually get made: benchmarks, not narratives.