bitcoin-kernel / browser-node — following the tip (testnet4)

This page follows the live testnet4 header tip. It syncs headers to the current tip, then keeps watching — each time the network mines a block, the new header is validated (proof-of-work, BIP94 difficulty, linkage) and the tip advances, right here in the tab. Reorgs are handled. the running node · the acts
Scope: this validates the header chain, not full blocks (scripts/signatures need the full UTXO set — the 25 GB wall). It follows the tip; it doesn't fully validate each new block's transactions.

idle

header tip (live)

—

network tip (peer)

—

new blocks since open

—

last checked

—

polls the peer every 8s

reorgs handled

most-work chain

transport

—

Needs a bridge to a testnet4 peer (browsers can't open raw TCP): the local WS bridge (node bridge.mjs, default), or a WebRTC bridge — pass ?signal=wss://your.pod/.webrtc&room=<hex> (node bridge-webrtc.mjs on the other end).