𝐒𝐨𝐟𝐥𝐞𝐢𝐫𝐞 $𝐒𝐅𝐋𝐑 : 𝐓𝐡𝐞 𝐋𝐚𝐮𝐧𝐜𝐡 𝐅𝐚𝐢𝐥𝐞𝐝 𝐨𝐧 𝐅𝐞𝐞𝐬 𝐚𝐧𝐝 𝐋𝐢𝐪𝐮𝐢𝐝𝐢𝐭𝐲, 𝐍𝐨𝐭 𝐚 𝐇𝐚𝐜𝐤 – 𝐇𝐞𝐫𝐞 𝐈𝐬 𝐭𝐡𝐞 𝐒𝐧𝐚𝐩𝐬𝐡𝐨𝐭 𝐑𝐞𝐬𝐞𝐭 1. What happened: This was not a hack. No private keys were stolen, no contract was exploited by an attacker, and no “insider dump script” was run against the community. What happened was a configuration failure at launch. A large portion of supply was placed in Streamflow lock / custody contracts. On Streamflow, token locks carry a 0.5% token fee in addition to a small SOL creation fee. That fee is not a theory. It is part of how the lock product is priced. At market open, that fee interacted with a second problem: very thin liquidity relative to FDV. - FDV (fully diluted valuation) is price × total supply, including tokens that are not circulating yet. - Liquidity is the actual capital sitting in the pool that can absorb buys and sells without the price collapsing. If FDV is large and the pool is small, even a modest automatic sale can smash the chart. That is what the first announcement described: 0.5% of the locked supply was automatically liquidated at open because liquidity was too low against the FDV. So the sequence was: 1. Locks were created with Streamflow’s standard lock fee structure. 2. Market opened with insufficient depth. 3. The fee / custody configuration forced tokens into the market immediately. 4. Thin liquidity turned a fee event into a chart event. That is an operational and parameter error. The first statement already accepted full responsibility for it. 2. Why this matters more than “the chart looks ugly” In a healthy launch, locked supply is supposed to be off the market. Locks exist so holders can verify that team, treasury, or vesting tokens cannot hit the book on day one. When lock infrastructure itself introduces a token fee that must be settled at creation or open, two things have to be true or the design fails: 1. Someone has pre-funded the fee in a way that does not sell into the new pool. 2. The pool is deep enough that any residual sale does not define the price. Neither condition held. Low liquidity versus FDV is the classic launch mismatch: the market is priced as if the whole supply is valuable, but only a tiny float can actually trade. Any forced seller— fee, sniper, LP add error, or unlock—becomes the price. That is why the first message called it a severe miscalculation of configuration parameters, not a mysterious exploit. 3. Why the team is not “patching the current chart” After reviewing the options overnight, the second announcement rejected a bandage on the existing token. Patching a broken first print usually helps the wrong people: - Snipers / MEV bots already bought the dislocation. - Late liquidity providers and first-hour sellers already locked in the damage. - Day-one holders who bought the intended launch would be forced to compete with a chart that now encodes that failure. A repair that leaves the same mint, the same custody contracts, and the same tainted order book would not restore a clean price-discovery surface. It would mostly transfer remaining value toward whoever was fastest when the fee hit the pool. That is the stated reason for a new token instead of a cosmetic fix.
