How BEAM Works
Cryptographic attestation for every transfer. No trust required.
Why This Matters
Decentralized bandwidth networks need a way to prove work happened. Without verification, participants can claim rewards without contributing.
BEAM solves this with Proof-of-Bandwidth: cryptographic attestation that verifies actual data transfer.
The Mechanism
Every transfer generates a cryptographic proof. This proof attests that specific data moved through specific nodes at specific times.
Components
- •SHA-256 hash of data
- •Cryptographic timestamps
- •Hotkey signatures (unforgeable)
- •Canary bytes (anti-collusion)
- •Merkle aggregation (batch verification)
Overhead
~350 bytes
per 10 MB transferred
<100 μs
verification latency
99.996%
protocol efficiency
Three Layers
Validators (64)
Verify proofs. Assign weights. Distribute emissions.
Orchestrators (256)
Coordinate transfers. Manage worker pools. Submit proofs.
Requires 100+ TAO stake.
Workers (unlimited)
Move data. Generate proofs. Receive rewards.
Permissionless participation.
Verification Layers
Layer 1: Cryptographic
- Every attestation signed by participant hotkey.
- Canary bytes prove actual data receipt.
- Invalid signatures rejected.
Layer 2: Physical
- Timing validated against physics.
- Geographic claims verified via latency.
- ASN diversity prevents loops.
Layer 3: Statistical
- Validators spot-check transfers.
- Gaming has negative expected value.
- Honest participation is optimal strategy.
Why BEAM is Faster
Single connections have speed limits. BEAM splits transfers across multiple paths and aggregates throughput.
Example: 10 GB Transfer
Zero-Knowledge Relay
Data is encrypted end-to-end. Relay nodes move bytes without access to content. They attest transfer without knowing what was transferred.
Built on Subnet 75
BEAM runs on Bittensor. This provides: