HOMESTEAD
rules

THE SHEET

Every number the ranch runs on, from the same file the foreman reads. If a number is not on this page, it is not a rule.

the kernel, exactly
a = DN_x − 1000, b = DN_y − 1000 (Sentinel-2 L2A baseline ≥ 04.00 carries a +1000 offset) nodata: DN_x = 0 or DN_y = 0 → q = −32768 den = a + b; den ≤ 0 → q = 0 else q = trunc((a − b) × 10000 / den) clamped to [−10000, 10000] output: int16, row-major, little-endian, 512 × 512; hash = SHA-256 of those 524,288 bytes 20 m bands are read at half size and used nearest-neighbour: pixel (r, c) reads band[r ÷ 2][c ÷ 2] preview: 8 × 8 block mean (floor), nodata → 0, else 1 + ((mean + 10000) × 254) ÷ 20000

Same code in the browser (kernel.js) and on the ranch PC (ranch.py). Phase 0 proved the hash identical on Python, Node, Chrome and WebKit.

rejection reasons · every one the foreman can give
reasonwhat it means
why cheating does not pay

A hand that guesses a hash is caught by the second hand. A hand that colludes needs to control both copies of a random assignment and still pass the known plots, which arrive at random. Strikes reset credibility, three suspend the wallet, and the epoch cadence caps what any burst can extract. The map never says which plots are known.

Not yet in place, said plainly: per-IP limits, triple redundancy for new wallets, and the payout threshold. They arrive with the coin phase.

licence

Every harvest tile carries: “Contains modified Copernicus Sentinel data [year], processed by HOMESTEAD hands. Fire detections courtesy of NASA FIRMS.” Outputs are open; download them on the harvest page.