Flipper retweeted
Replying to @onchainflipper
damn bro this is the most lit branding for a twitter account of all time im legit jealous- i was about to rock the same pfp ngl lmaooo. high art ser
got this absolute gem from @tethegamer2 lying around here
my honest take on why @printr will fail
i dont understand why every single launchpad feels the need to reinvent the wheel just to end up with no real usp and think that doing "a little bit of everything" is enough to be the next "revolutionary" platform
in the intro tweet alone we already see like 8 features, most of which already exist in some form and/or mainly just add unnecessary complexity
i doubt the average trencher will be able to keep track of all the options when launching on printr, let alone when looking at the configuration of each individual feature
endless launch options wont fix the trenches
8 chains
5 different fee distributions with custom parameters
4 different token profiles with custom starting and graduation marketcaps
3 different supply options
all of that combined with little to no support from the main trading terminals to even display these options, unless you also keep the printr site open next to your terminal just to see whats going on
especially considering they decided to build on the meteora bonding curve, where by now everyone knows that once enabled in terminals the feed is flooded 99% of the time with fake coins mainly used for money laundering, while at the same time also failing to clearly differentiate themselves (and their users tokens) with any kind of printr branding
in their intro they say "we spent months listening to the trenches" and i honestly think thats exactly what didnt happen here
the sentiment in the trenches has been pretty clear: users are fed up, fed up with unnecessary features that either dont get used or just end up diluting whats left of the liquidity
once again: too much, poor execution, and badly positioned from the start
Flipper retweeted
Replying to @jeetassassin @json1444
lets start with mass deploys:
add a required co-signer to the create + createV2 instruction in the pf program so every launch tx must be co-signed by your backend
then add a captcha to your launch ui that gets verified server-side before co-signing to prevent direct automated api calls using privy jwts / cookies
et viola - mass deploys solved without adding a deploy fee
xitter.cf/json1444/status/204192…
Replying to @jeetassassin
the bonding curve is a permissionless product. anyone can build tooling on top of it, so disabling 3rd party tools isn't a realistic solution
I'm curious to know which specific tools you dislike, as there's potentially tangible solutions on the interface side of things (Terminal, pump app, etc.)
Flipper retweeted
this has effectively been running by "someone" since creator fees launched
two finetuned models, trained on the full dataset of ~13m pump launches at the time
model one estimates launch probability per tweet, trained on historical data mapping tweet content, topic, and account to actual downstream token launches
including how many tokens were historically launched from similar tweets or similar accounts
runs in <250ms and autonomously decides whether its worth launching or not
model two generates name and ticker, trained on historical token naming decisions to model how specific topics and tweet contexts shape naming patterns
for example, it quickly learned that when a person or animal dies or gets injured, tokens in the past were often named “justice for ... ” so it adapted its name and ticker outputs, something you would never achieve without your own finetuned model
you are starting a game here that someone else already won a long time ago, and it wont work for the masses
turns out when they said "keep building" they meant we'd actually end up back on a construction site










