One Block enters controlled Bitcoin mainnet operation

One Block has moved from dry-hash testing into a controlled Bitcoin mainnet experiment.

The worker receives templates from a locally verified Bitcoin Core node, constructs a coinbase transaction for the configured public payout script and hashes at a deliberately low CPU target. A block is submitted only if its hash satisfies the network target. Private keys are not loaded by the worker or dashboard.

What is operating

• Bitcoin Core 31.1 is synchronized and validates the chain locally.
• The mainnet worker runs as a persistent macOS service.
• A loopback-only dashboard reports node, worker and search telemetry.
• The public payout address is masked in screenshots and UI exports.
• Battery and thermal safeguards reduce or pause work when required.
• Counters for hashes, templates, stale templates, candidates, submissions and accepted blocks persist locally.

Before the live gate opened, the system completed node observation, dry-hash validation, restart persistence, Wi-Fi reconnect and sleep/wake checks. The 24-hour endurance run was completed; one CPU-only acceptance threshold was recorded through a documented operator override rather than presented as an unqualified pass.

What this does not claim

This is not a promise of mining revenue and it is not presented as a competitive mining system. A laptop-scale hashrate has an extraordinarily small probability of finding a Bitcoin block at current network difficulty.

The purpose is narrower: build a transparent, self-custody engineering experiment that can be inspected while it operates. The dashboard therefore shows zero candidates and zero accepted blocks until the software has real evidence to report.

The experiment remains intentionally conservative: low resource use, local validation, no private-key custody and no automatic claims of success.