Sun God 🐶

"no block 0." i checked 12 launches. the same wallet bought 6 in block 0 and the other 6 one slot later. that's a hell of a feature promise you aren't holding up to. i don't want to FUD anyone. i love seeing teams trying to make the trenches less shit. but when a promise is this easy to disprove, i'm going to say something. stonk, ember, bonk and bags are technically interesting to me. from what i've seen, they aren't bullshitting about what they've built. that's the standard i'm aiming for with @payperfun too. quick disclosure: i'm building payper alongside my other companies. so yes, i have a horse in this race. i'm also a tech guy. studied computer science, successfully dropped out about 30 years ago because i was making too much money too early, and never stopped building. honestly, i wouldn't know what else to do. which is probably why this stuff annoys me. launch says: "Nobody can be in the block it is created in." uselaunch.fun/how except someone was. $MACHINE was created in slot 462041763, transaction index 294. another wallet bought 16.98 million tokens, about 1.7% of the initial supply, at index 343. same slot. successful buy. finalized onchain. creation: solscan.io/tx/3sV24P4CEsR8tB… buy: solscan.io/tx/CPT4WFUVmzrMgW… it wasn't a one-off. in the twelve-launch sample, that wallet bought MACHINE, SUPERIOR, LAUNCHERS, OU, 1OF1 and SQUAD in their creation slots. the other six buys landed exactly one slot later. subsequent sells showed up for eleven of them. WEINER after one second. SAME after two. SUPERIOR after seven. here's SUPERIOR, both transactions in slot 462040849: creation: solscan.io/tx/5WoYNhNhXAhzKL… buy: solscan.io/tx/5K6bjkJdCVTrtB… looks very much like automated sniping. i don't know who owns the buyer wallet. it's a different address from the master wallet. no direct connection was found, but that doesn't prove independence. i'm not inventing an insider story when the actual transactions already disprove the promise. a private bundle with a tip doesn't reserve an entire block. it doesn't stop another transaction buying afterwards in the same slot. docs.jito.wtf/lowlatencytxns… "no vamps" needs some honesty too. rejecting duplicate tickers and images on your own pad is useful. your database can't stop someone copying a coin elsewhere. just say what the protection covers. and to be precise: they've moved to their own Raydium LaunchLab platform. older coins remain on Stonk. using existing infrastructure is fine. PAYPER does that too. the LARP, to me, is selling an absolute technical guarantee that a few onchain checks can disprove. in any business i've built, we'd have to fix that claim or fix the product. a green chart wouldn't change the conversation. i'm not saying everything they've built is fake. i'm saying "no block 0" is false in these examples, and they should stop promising it. same standard for PAYPER. if we say something the product doesn't do, call us out.

it’s easy. just ignore pump tokens. don’t ape them. deselect pump in your terminal filters. try @LaunchOnSF, @embercurve, @bonkfun, @BagsApp or our new experiment, @payperfun. one week in: $14.5k paid out to profiles, 3.4% burned, and a $161k ATH for the platform token. receipts: payper.fun/proof