A dedicated high-throughput lane between two connected devices for big transfers, one fast hop within a mesh that's still carrying ordinary peer traffic all around it.

How it works

A connection-oriented L2CAP channel (CoC), a real byte stream, far faster than GATT notifications.
Bulk traffic, HTTP responses, files, media, rides this lane; small control frames stay on GATT.
It's one fast hop between two connected peers, inside the larger store-and-forward mesh.

Why it matters

For developers

Bulk automatically uses the CoC stream; you don't select it. (On BLE, this is an L2CAP connection-oriented channel.)

For business

Large transfers move at usable throughput instead of trickling through a control channel.

Deeper implementation detail is coming in the Hop whitepaper.

← BLE Internet relay →

Direct data channel

Ready to build on it?