Bluetooth file transfer

How it works

Bluetooth bandwidth is low compared with Wi-Fi. A 20 MB PDF works. A 2 GB video is the wrong radio. Pairing is the access control. There is no object store and no audit log in your portal.

Two phones exchange a 15 MB brief over Bluetooth in under a minute. The same phones fail a 1 GB attempt and switch to a link. The brief never touched a server. There is no revoke.

How it differs

Bluetooth is not Wi-Fi and not AirDrop, though AirDrop may use a Bluetooth discovery step and Wi-Fi for bytes.

An unpaired send to a discoverable device can offer a file to a stranger nearby.

Require acceptance.

On the ticket

• The practical close is a log line: time, actor, byte count, result.
• Without that line the transfer is a story.
• With it, the next person can see whether this door did what the ticket claimed.
• If the path is shared, say so in the partner profile so a later change does not silently pick a different limit, key, or region.
• On a real ticket, write down the door, the byte count, and the clock.
• For bluetooth file transfer, that means naming the host or bucket, the expected size, and the time the other side must have a complete file.
• A progress bar is not that record.
• A 200 response that arrives before the complete call is not that record.
• If a retry is allowed, say how many and whether it resumes.
• If a person must approve the send, name the person.
• Partners who receive bluetooth file transfer files should match on hash or size before they import.
• A same-length corrupt file passes a size check and fails a hash.
• Keep the published hash off the only channel an attacker can edit, or treat it as a corruption check rather than a substitution check.
• When the path changes, new key, new region, new cap, update the profile the same day so the next run does not use a stale limit.