Been digging into the Sender vs Stockthereum drama. The on-chain picture is pretty different from the narrative that's been going around on CT. The original complaint - $STOCKER called out $SEND for an LP issue. That part was partially real: early Sender launches were seeded so the curve ran out before infinity. Which is an easy enough fix, has happened before in the space and resolved easily. What Sender did about it - For $SEND , supply was manually added into the upper ranges and burned, so liquidity holds past that point. It appears a lot of the teams on legacy tokens also went out and added lp above the range to stabilize (check the chain). New launches were changed to seed correctly from the start. So the bug existed, and it got fixed on-chain. Kind of bullish. Now it gets funny - Compare Stockthereum's contracts to Sender's and they're built on the same code! They literally copied the sender code, plus they don't know how to fix the issue. What that means - So tokens launched on Stockthereum are hitting the same liquidity wall in the upper market cap range. As of today, I can't find any sign they've patched it. And $zip pool (their runner) has basically no tokens left when it ranges up. None that are revoked. TLDR The platform and metamoon spent so much time pointing at Sender's LP bug appears to be running a copy of the same code, BUG INCLUDED, without the fix. If you're holding tokens on Stockthereum, pull up the contract and check the LP ranges before you size up. Regards
Evidence timeline
X and Telegram posts, app-native calls and on-chain activity linked to this asset.
$ZIP 209k - 9.6x Near 10x in 1 hour. Launch a coin on Pons, paired with anything. Zip it to trade privately. CA: 0xe80e5864550d0f1b69b8063bd03571bbe722ff9e Chart: Early calls:
Been digging into the Sender vs Stockthereum drama. The on-chain picture is pretty different from the narrative that's been going around on CT. The original complaint - $STOCKER called out $SEND for an LP issue. That part was partially real: early Sender launches were seeded so the curve ran out before infinity. Which is an easy enough fix, has happened before in the space and resolved easily. What Sender did about it - For $SEND , supply was manually added into the upper ranges and burned, so liquidity holds past that point. It appears a lot of the teams on legacy tokens also went out and added lp above the range to stabilize (check the chain). New launches were changed to seed correctly from the start. So the bug existed, and it got fixed on-chain. Kind of bullish. Now it gets funny - Compare Stockthereum's contracts to Sender's and they're built on the same code! They literally copied the sender code, plus they don't know how to fix the issue. What that means - So tokens launched on Stockthereum are hitting the same liquidity wall in the upper market cap range. As of today, I can't find any sign they've patched it. And $zip pool (their runner) has basically no tokens left when it ranges up. None that are revoked. TLDR The platform and metamoon spent so much time pointing at Sender's LP bug appears to be running a copy of the same code, BUG INCLUDED, without the fix. If you're holding tokens on Stockthereum, pull up the contract and check the LP ranges before you size up. Regards