Josh's 6 October 2026 ask: deep backward and forward research across the hash, finality, economy, network and every shipped surface. This commit carries the first three lanes. - docs/analysis/horizon/algorithm.md: the chip model on the 6 October numbers (f = 1 GDDR7 chip 5.7x per joule against the 5090 at class v3, 2.1x at class v4 with k = 1), the FPGA lane tightened to 0.30x to 0.47x per watt, the reserve R0 to R8, the reconciled shadow-N ladder (section 5.3a) with HBM4 and three verifier brackets, the first measured verifier proxy on igneum-build-1 (class v4 5.06 ms cold, dr736 10.51: out), the dataset schedule to 2030; model sim/horizon/algorithm/model.py. - docs/analysis/horizon/frontier.md: sixteen ideas ranked by payoff over difficulty with the Monero and Kaspa attacks, prior art cited, the honest never column; model sim/horizon/frontier/frontier_model.py. - docs/analysis/horizon/new-pow.md sections 0 to 4: three new proof-of-work schemes defined, reviewed in two personas, scheme A (mining is proving) ruled out on bytes and sampleability, B and C in prototype on two rented 4090s; measured rows follow. - docs/analysis/horizon-2026-10.md: the summary skeleton and the lane table. Every rental cost cites docs/bench-log.md "Rental cost of hash, 6 October 2026". Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| frontier_model.py | ||
| out.md | ||
| README.md | ||
sim/horizon/frontier
Lane 7 (frontier) of the Horizon programme, 6 October 2026. One script, pure Python 3 (no numpy):
python3 sim/horizon/frontier/frontier_model.py > sim/horizon/frontier/out.md
It prints the arithmetic behind docs/analysis/horizon/frontier.md: the 2030 predictions (VRAM, memory
dollars, random-read ceilings for GDDR7, HBM3 and HBM4, the stored-dataset chip under the latency shadow,
zkVM cost per Ethereum block, the 2028 prover tiers), the rental-tax reward rule, the work-stake bond,
the burn-funded bounty, the GPU-rental settlement comparison, the 30-s beacon and the proving-income
ceiling. Every input carries a label (measured, cited, designed, approximate) and its source in the
INPUTS table at the top of the script and of the output. Run on the Mac without the lock: it is
arithmetic, not a measurement (about 50 ms).