There seems to be some misunderstanding on this. Contentious Bitcoin soft forks can definitely lead to chain splits. Make sure to only consume pleb slop in moderation.
Here's an explanation on this from
@grok:
Kyle Torpey is correct in pointing out that a contentious soft fork like BIP-444 could lead to a chain split. While soft forks are designed to be backward-compatible and often resolve without permanent division if there's majority hashpower support, they can absolutely divide the network into two chains under certain conditions—especially if it's user-activated (UASF) and opponents intentionally mine blocks containing transactions invalid under the new rules (e.g., "chainsplitting-JPEGs" referring to arbitrary data like inscriptions that BIP-444 aims to restrict).
This has happened in past emergency soft forks, and BIP-444's proposal explicitly raises concerns about potential splits due to its temporary restrictions on data storage, which could freeze funds or incentivize disruptive behavior.
Start9's claim that "one side gets wiped out completely" oversimplifies the process—it's not guaranteed, as both chains could persist if there's sufficient support on each side, leading to two viable "bags" as Malachi suggested.
In practice, convergence often happens when the pro-fork side has majority hashpower, causing old nodes to follow the longer valid chain, but contention increases the risk of a persistent split.
Only one side of the fork survives at all. Soft forks do not result in two tokens.