receive by light

catch a code

point this phone's camera at a code on another screen. what it carries stays on this phone. nothing goes over the internet.
a code is never acted on by itself. you see it first.
can this phone do it?
checking this phone…

…

…
see the whole receiver
the picture never leaves this phone.

the eye

tap the eye to open it
works herenot hereframe caught
bLighTnetWorK://receive · light, never network
payload → act = refused shape here, signatures in the ceremony
probestatemeasured

receive pipeline · full duplex

    conversation · read from this page, now

    verify · no trust in this page needed
    1. devtools → network while a beam lands: zero requests
    2. bcomb.selfTest() in the console: frames drawn and read back here
    3. the reply is signed with a key made on this device; check it on the other side
    the raw log below fork the template ↗ (opens in a new tab)

    the whole receiver

    Receive on the bLighTnetWorK

    ~588 b/sec · bLighTnetWorK

    Point this camera at a BNR code on another screen. The payload arrives as a bLiGhTbeAM — light, never network — and stays on this device. This device answers back: its screen becomes the return beam.

    Camera first.
    Grant the camera once — this device remembers it — then hold it on the other screen. Frames arrive in any order; a missed one comes round again.
    Eye camera in · reading the beam
    Conversation what the two devices are saying
    bLighTnetWorK
    Nothing heard yet — start the camera and aim it at a beam.
    [bLighTnetWorK] ready.
    bLighTnetWorK receiver · single-frame bLiGhTbeAMs (≤2.9 KB) · streamed beams (>3 KB) are the fountain lane · this page validates shape; the consuming ceremony verifies signatures. It never acts on a payload alone.
    ⌂ hub