February 2026 may be remembered as the month amateur radio gained its fastest weak-signal mode — and immediately fractured it. A new HF digital protocol called FT2 promised to push the FT-family (FT8, FT4) into ultra-fast territory: ~4-second QSOs, contest-level throughput, and weak-signal capability that could change how operators compete and DX on HF. The excitement was real, and the early on-air results were promising.
But within days of its first on-air tests, FT2 split into two incompatible implementations, igniting what operators are already calling the “FT2 war.”or ” FT2 Schism”
This isn’t the familiar FT8-versus-tradition culture clash. It’s something rarer in ham radio: two protocols with the same name, the same purpose, and the same timing — but completely unable to talk to each other.
The conflict centres on two independent developers and their software ecosystems.
Decodium FT2 — by IU8LMC
The first FT2 implementation appeared on air in mid-February 2026 inside Decodium, a WSJT-X-derived application developed by Martino, IU8LMC. It demonstrated:
- ~3.8 second T/R cycle
- ~240 QSOs/hour theoretical rate
- FT8/FT4-style structured messaging
- Successful, verified HF contacts
This was the first time “FT2” existed outside theory — real QSOs, real decodes, real excitement. The ham radio digital community took notice immediately.
WSJT-X Improved FT2 — by DG2YCB
Ten days later, an independent FT2 mode appeared in WSJT-X Improved, developed by DG2YCB. It targeted the same operating niche:
- ~3.75 second cycle
- High-rate contesting operation
- FT-family style workflow
But there was a critical problem: the two FT2 modes are not interoperable.Stations running Decodium FT2 cannot decode WSJT-X Improved FT2, and vice versa. They occupy the same conceptual space but speak entirely different digital languages.
Why This Became a Feud FT2 Schism
Mode fragmentation isn’t new in amateur radio. But the FT2 split escalated quickly because three sensitive issues collided at once.
1. Priority vs. Independence
IU8LMC’s supporters point out that Decodium FT2 was first on air, with working QSOs as proof. DG2YCB’s supporters counter that “FT2” is a generic concept, not owned by any single developer.
When WSJT-X Improved released its FT2, IU8LMC publicly remarked:
“I offered a handshake. He chose a race.”
The dispute shifted from technical to personal almost immediately.
2. Open-Source Tension
WSJT-X is GPL-licensed. Some community members questioned whether Decodium’s FT2 implementation had released sufficient source code, while others argued that forks commonly diverge and release on different timelines.
In ham digital culture — where collaboration norms run deep — perceived licence violations trigger strong reactions. The FT2 split tapped directly into that sensitivity.
3. Fear of Activity Fragmentation
HF digital modes depend on critical mass. Two incompatible FT2 implementations mean:
- Split calling frequencies
- Split decoders
- Reduced QSO probability for both user bases
- Genuine user confusion about which software to run
Operators immediately asked the practical question: Which FT2 should I run?
That is the moment a technical fork becomes a “war.”
Technically Similar — But Not Compatible
Both FT2 designs aim at the same operating niche: faster than FT4, better weak-signal performance than MSK contest modes, structured minimal QSOs, and automated sequencing. The goals are identical.
But digital modes aren’t defined by goals — they’re defined by exact symbol mapping, interleaving, and coding choices. Even small differences at the encoding level produce total on-air incompatibility.
So despite sharing the FT2 name and targeting the same T/R timing, the two protocols are mutually unintelligible. A station cannot accidentally decode the wrong FT2 — the signal simply won’t resolve.
Rare Kind of Split in Amateur Radio
Amateur radio has seen software forks before. WSJT-X vs JTDX, various fldigi variants, and competing contest logger ecosystems are all familiar examples. But those forks usually preserve on-air compatibility — operators can still make QSOs across different programs using the same underlying protocol.
FT2 is fundamentally different. This resembles a protocol fork — closer in nature to the historical JT65 vs JT9 divergence — except both branches claim the same mode name and the same operational purpose simultaneously.
That’s why the community reaction has been unusually intense for a mode that is only weeks old.
What Happens Next? FT2 Schism
Based on how similar disputes have played out historically in amateur radio and open-source software, a few outcomes are possible:
1. One FT2 wins adoption — the community converges on a single implementation through organic preference, and the other fades from use.
2. Rename and coexist— one branch becomes “FT2-X” or a similar variant, allowing both to survive without the naming conflict.
3. Merge or alignment— the developers reconcile technical differences and unify the protocol under a single specification.
4. Both fade — FT2 fragmentation prevents either version from reaching the critical mass needed for regular on-air activity, and FT4 remains the fast FT mode of choice.
Right now, it’s too early to know which path FT2 will take. The community is watching closely.
More Than a Mode Dispute FT2 Schism
The FT2 conflict highlights a deeper truth about modern amateur radio that is easy to overlook. Digital modes now evolve like open-source software projects — complete with forks, licence disputes, governance questions, and community alignment pressures. When protocols are software-defined rather than hardware-standardised, technical divergence can happen faster than social consensus can form around it.
FT2 didn’t just push speed boundaries. It exposed how fragile agreement can be in a decentralised innovation culture — and how quickly a genuinely exciting technical development can become a community flashpoint.
Whatever happens next with FT2, the episode is a useful reminder that in amateur radio’s digital mode ecosystem, the hardest problem isn’t usually the coding scheme. It’s getting everyone to agree on which coding scheme to use.
Related Posts
- FT2 – A New Digital Mode Hams Are Starting To Spot (February 18, 2026)
- FT2: The Fastest Digital Mode in Amateur Radio (February 19, 2026)
- FT2 Digital Mode: Speed King With Serious Growing Pains (February 20, 2026)
FT2 Schism