bizzle bizzle
···· no peer

Move a file between two screens

No network, no cable, no account. One screen shows QR codes; the other reads them with its camera.

  1. Scan this with your phone's normal camera app.
  2. bizzle opens there, already linked to this screen.
  3. Tap Start camera on the phone, then press continue here.

One screen cannot show the pairing code and the data at once. After a few seconds this starts alternating between them, so the phone links up on its own — or press continue to go straight to sending.

Already open on the other screen? Use this device as the camera.

Start something

Workspaces

The same link, set up for a particular job. Reachable any time from the menu.

Sound link

The same frames, carried by air instead of light. Two lanes of sixteen tones sounded together, one nibble in each — above almost anyone's hearing, and far above an aeroplane, which is enormously loud but almost entirely below 500 Hz. No network, no line of sight, nothing to pair: the other seat only has to be within earshot.

Off. Nothing is listening.

Sound carries to everyone in earshot, not to one seat — so treat it the way you would a room with other people in it. A dead drop sealed with a passphrase stays sealed whichever carrier moves it.

Dead drop

Sealed here, opened there. Everything the screen shows is ciphertext, so a camera in the room, a shoulder, or a photograph of the frames gives up nothing without the passphrase.

Nothing sealed yet.

Split a picture

The same passphrase above, made visible. One plane is the keystream it derives; the other is the picture with that keystream subtracted from it. Neither is anything on its own — and laid over each other they are not showing you the picture, they are computing it, because difference and exclusive‑or are the same operation at one bit per channel. Print the two on transparencies and it still works on paper.

Choose a picture and it becomes two planes of noise.

Nothing split yet.

Opened here

Sealed items that arrive will appear here.

Share

Photos are re-encoded before sending unless you say otherwise — at a few kilobytes a second that is the difference between seconds and half an hour.

Watching
Confirmed
0

Payment request

URI


Air-gapped signing

Hand an unsigned transaction to a device that has never touched a network, and take the signed one back — over light, in both directions.

Never type a seed phrase or a private key into any page, including this one. This screen is for transactions and addresses. Interoperability with hardware wallets that speak animated BC-UR is not implemented — today both ends have to be bizzle.

Send something

Drop a file here, paste, or .

Split into chunks and shown as QR codes. Nothing leaves this device.

    This screen

    Frame
    hello
    Version
    Payload
    Rate

    This camera

    0 fps 0 frames
    Point it at the other screen

    Back up

    Whatever you put in becomes one compressed container. That container is what you download, what you copy as text, and what the frames below encode — so nothing downstream has to care what the originals were.

    Choose files to build a container.

    Restore from frames

    Import the pictures back — exported frames, screenshots, or straight-on photographs of them. Order does not matter and neither does how many are missing, so long as enough remain. Rotated or angled photographs are not read.

    Restore from text

    Messages

      This device
      When a transfer finishes
      Send without a back-channel

      A higher QR version packs more bytes into every frame but needs a sharper camera. If frames stop decoding, drop the version or raise error correction.

      Protocol log