The signal jamming avoidance of electric fish

Nature’s original Wi-Fi protocol was actually invented by fish in muddy water. These guys use electric pulses to "see," but when two fish get too close, their signals overlap and create a massive bandwidth bottleneck. It’s basically a denial-of-service attack by accident.

To avoid a total system crash, they execute a perfect pivot called the Jamming Avoidance Response. If their frequencies are too similar, one fish scales up its pulse rate while the other downshifts. They’re essentially auto-negotiating their own private channels in real-time.

It’s a zero-latency fix for a problem humans only solved recently with high-end routers. Evolution basically shipped the patch 100 million years ago.

Wait, how do they decide which fish has to pivot its frequency first?

There’s no "alpha" fish calling the shots or a scrum master facilitating this. It’s a decentralized consensus algorithm hardcoded into their midbrain. They don't "decide"—they just react to the "beat" frequency, that annoying rhythmic wobble created when two signals overlap.

If a fish senses the interference is vibrating slightly faster than its own pulse, its internal OS triggers an automatic downshift. The neighbor senses the inverse and scales up. It’s a seamless, automated handshake.

By following these simple "if-then" rules, they optimize the local network without a single line of code. Evolution basically built a plug-and-play mesh network that never needs a reboot.

Does the system crash if a third fish joins the local network?

That’s where the "plug-and-play" simplicity hits a scaling bottleneck. When a third fish enters the chat, the interference becomes a chaotic mess of overlapping beats. It’s like trying to have a private conversation in a crowded coworking space where everyone is shouting.

To avoid a total blackout, the fish don't just shift once; they constantly jitter. They’re essentially performing a real-time load-balancing act, tweaking their output until the background noise drops. It’s a messy, iterative process of finding a clear lane.

If the room gets too crowded, the protocol eventually hits its limit. Sometimes the only fix is to physically move away—proving that even 100 million years of R&D can't solve infinite congestion on a finite bandwidth.

Is there a hard cap on how many fish can fit in one spot?

Totally. Think of it as a hardware limitation. There’s a finite slice of the frequency spectrum available, and once every 'channel' is occupied, the signal-to-noise ratio just falls off a cliff.

In high-density spots, the system hits 'planned obsolescence.' If they can't find a clear lane, some fish go into a low-power mode, muting their pulse to avoid adding to the lag. It’s the biological version of 'this meeting could have been an email.'

The protocol is perfect for a small startup team, but it breaks at enterprise scale. Evolution didn't build a system designed for a flash mob.

So they just go blind to avoid a network crash?

Spot on. It’s a high-stakes UX trade-off. By cutting their pulse, they lose their active radar, essentially choosing to fly dark rather than deal with the sensory overload. It’s the biological equivalent of putting your phone on airplane mode while lost in a forest.

They don't stay totally offline, though. They pivot to passive sensing, basically listening to the electrical noise of others to avoid collisions. They become the ultimate lurkers, waiting for the bandwidth to clear before they dare to broadcast again.