here is my hypotheses on new @bankrbot x @SushiSwap launchpad is their solution as an answer to @TradePools currently, bankr use @dopplerprotocol and @Uniswap v4 as its infra under the hood. when ethereum:0x1f9840a85d5af5bf1d1762f925bdaddc4201f984 decided to make their own launchpad - they literally vampired users and liquidity from 67 launchpads who used uniswap's rails. which @0xDeployer didnt like He found a kindred spirit in @alexmccurryo who is uniswap's competitor and told that frogs are lame so you are here at pools[.]fun teaser. my working theory: poolsfun moves bankr's existing robinhood launch flow from doppler/uniswap v4 to sushi launch and sushi v3. bankr keeps the distribution layer: > launch a token through a message on x > launch through the bankr agent, api or cli > managed wallets and transaction execution > metadata and social links > creator fee claims and recipient routing > treasury automation > glidepath for gradual creator selling sushi becomes the execution and liquidity layer: > immediate sushi v3 market > permanently locked lp position > launches against weth, usdg and tokenized stocks like tsla, nvda, gme and aapl > a simpler fixed launch recipe targeting roughly $5k initial fdv pros and cons? > the current bankr/doppler stack charges 1.75% all-in per trade > the current sushi launch pool charges 1% that is roughly 43% less fee friction for traders. it also gives bankr a dex partner that is less likely to take over the frontend, user relationship and launch distribution itself but a straight backend swap has serious downsides - under bankr's current doppler economics, 0.95% of volume works for the creator side: > 0.665% claimable creator fees > 0.285% compounded into locked liquidity under the existing sushi launch economics: > the creator gets 0.70% > sushi gets 0.30% > and sushi also reserves 3% of every token supply for one year on $1m volume: > current bankr creator side: $9,500 > current sushi creator fees: $7,000 the existing bankr stack also has a 0.475% bankr protocol fee and a 0.2375% bnkr buyback. neither exists in the current sushi factory sushi v3 is also less programmable than the v4 hook stack. bankr's quote-only fees, custom fee routing and bnkr buyback do not automatically survive the move. and sushi launch is not a fair-launch upgrade the creator can still launch and buy the virgin pool atomically before anyone else. there is no auction, anti-sniper window or crowd price discovery so just replacing uniswap v4 with sushi v3 would be cheaper for traders, but worse for creators and economically pointless for bankr for pools[.]fun to make sense, something else probably has to ship: > a bankr-specific fee split or router > an offchain revenue agreement with sushi > bnkr buybacks funded from the sushi side > bankr treasury automation around creator fees > or a much stronger consumer product that makes up for lower fee capture with far more launches and volume so base:0x22af33fe49fd1fa80c7149773dde5890d3c76f3b trying to own the launchpad distribution while base:0x7d49a065d17d6d4a55dc13649901fdbb98b2afba supplies the markets. we still need the actual reveal to know the fee split and whether bankr built a new router but that is the version that makes the teaser make sense get rich or die tryin'

new product by @TheIndexFi which will fit nicely on @ponsdotfamily - it deployed couple hours ago so you've never seen this link/screenshots/etc before. everyone benefits: > pons - new product on top of existing infra > creators - new narrative, attention > users - dividends > index - new cash inflow and its nice v4 case study. so how this works? tldr - token creators will be able to pay their token holders with dividends in stocks just like Index doing themselves with their holders. so every coin gets a treasury. details: > a creator picks a basket of tokenized stocks > chooses how much of the remaining fees go to holders > gets a deterministic treasury address before deploying the treasury > launches the coin on @PonsEcosystem and sets creatorFeeRecipient to that address > $pons escrow starts accruing fees immediately > the keeper binds the coin and each payout round buys one stock for that coin's holders so creators are buying a product for their own bagholders: recurring $NVDA, $SPY, $QQQ, $AAPL or a custom stock basket, paid from the coin's own trading fees. whatever share the creator does not send to holders stays claimable by the creator Indices clips a fixed 10% of everything routed through the treasury. receiver split(): > 50% buys $INDEX through the canonical pool and sends the bought tokens to DEAD > 50% becomes USDG and goes to the existing USDGBuyerDistributor > that distributor buys tokenized stocks and pays them pro rata to $INDEX holders > the buyback itself crosses the existing 3% INDEX hook, adding another stock-buying stream so the flywheel is: pons coin volume → creator fees → stocks for that coin's holders → 10% Indices cut → 50% $INDEX buyback + burn → 50% stock rewards for $INDEX holders this is how $INDEX rewards stop living off organic $INDEX volume alone. every opted-in pons coin can become an external revenue source all of this shipped today: > 19:34:57 UTC - early factory deployment > 21:23:27 UTC - current IndexTreasuryFactory deployed > 21:51:23 UTC - protocol receiver deployed > 21:51:24 UTC - receiver wired into the factory > 21:56:14 UTC - the current TLS certificate for became valid > 23:07:15 UTC - first treasury deployed > 23:10:29 UTC - first treasury funded with 0.1 ETH > 23:32:33 UTC - frontend redeployed again while I was tracing it contracts: > factory: 0x3450cEdfDD7F1082D766c8B8998C326D3696E8Df > implementation: 0x6bDc8993Dc922DC32E33A9c654b795AF53005C8e > protocol receiver: 0x0f5A32F791f536482d5BA27A58749F02c8b0cBbC > stock distributor: 0x2459DedB3012d1E929EdD17DF26620120bDF11bf > first treasury: 0xFACA543C31693d504B598222DEafaA59F720C978