Live on BSV mainnet
The Bitcoin light client
nobody can switch off.
One transaction output on the BSV blockchain holds a full Bitcoin light client. It checks every header it is handed — the proof-of-work, the difficulty, the clock — and anyone on Earth can hand it the next one for a fraction of a cent. No owner. No off switch.
verified tip
—
The leading zeros are the work. The beacon checked every one.
Proof it’s alive.
Every advance is a public transaction on the BSV chain, and the Bitcoin headers it verified travel inside it. Open one.
- Loading the lineage…
The weight of the chain.
Every header carries proof-of-work. The beacon checks it, adds it up, and carries the total forward.
2—
double-SHA256 computations stand behind the verified tip. Rewriting it means redoing them.
What a machine like this is for.
Other contracts on BSV can read the beacon’s verified tip — free, in script, with no oracle and nobody’s word to take. That one primitive, “what did Bitcoin actually say,” unlocks a family of things:
- Randomness nobody picked
- The hash of a future Bitcoin block is entropy no operator can choose or foresee. A dice hand, a lottery draw, a validator shuffle — settled fairly even if the house disappears mid-game. This is the settle-beacon arm of dHouse.
- Pay when Bitcoin confirms
- A payment that releases itself when a BTC transaction reaches six confirmations — proven in script against the beacon, not by an exchange’s API. Trustless BTC⇄BSV settlement rails.
- A citable record
- Checkpoints freeze “Bitcoin’s tip was this, backed by this much work, at this moment” under a transaction id. Auditors, courts, and other chains can cite it forever.
- Bitcoin’s clock, on tap
- Anything that should happen “after Bitcoin block N” — vesting, escrows, dead-man switches — can be gated on a verified height instead of a server’s clock.
Anyone can advance it.
Advancing the beacon means handing it the next headers and a few hundred satoshis for the miner. It checks the work itself — if the headers are real, it moves. If they’re not, it refuses.
- No account
- There is nothing to sign up for. The beacon doesn’t know who you are.
- No permission
- No operator to ask, no key-holder to wait on. Valid headers are the only credential.
- No real cost
- A few hundred satoshis per advance. Keeping pace with Bitcoin costs about half a cent a day.
This instance advances on a schedule.
Public cranking opens with the full genesis-synced beacon.
A fact you can cite.
A checkpoint freezes the verified tip — height, hash, accumulated work — under a transaction id anyone can look up forever.
- Loading checkpoints…