ShaTwo56 retweeted
launchpads might be the problem
in the memecoin golden era, tokens had no tax, and if they had, they were going towards its LP or its holders
look at the pre-launchpad memecoins, and look at how they fell when launchpads became a thing
launchpads have extracted a few billion dollars that would today sit in people’s wallets or in token liquidities
gg
ShaTwo56 retweeted
bonding curves were just a copypaste of regular AMM curves
I think in early 2024 raydium didn't support virtual SOL and launchpads were forced to implement their own curves, that allow trading without having any liquidity in the pool
it was a straightfoward implementation of initial distribution of coins and it did work, but rn it's getting played hard
imo the last hope for reviving the onchain trenches is hooks (SPL hooks and V4 Hooks)
i think once it gets decent exposure, people are gonna experiment on different distribution mechanics, and we are gonna see smth that naturally solves all the problems we have
well at least there's still hope
Bring back direct On-Chain deployment and watch the trenches heal, no more one click vamps, no more serial deployers pushing 10k token a day, less liquidity dilution and no more pumpfun max extracting from people. All it takes is stop playing their game. Another way is possible.
decided to look at a pumpfun token someone called on tg
7500 previous deploys, 44% cluster, Vamped by RapidLaunch
yeah it's fucked
droitardés et gauchiasses de tous pays, unissez vous... ! pour avoir les pires takes possible sur X point com!
ShaTwo56 retweeted
wow weird all the accounts shitting on the french protestors normally post pro Israel content. Must be a coincidence or something
Les salopes de droites passent leurs journées à jouer les chevaliers, à chialer sur le système H24 sur twitter, mais dès que ça commence à chauffer ça se chie dessus et ça soutient les FDP (force de police) macronistes
Can developers stop naming projects "openxyz"? Typing open + Tab in the terminal and watching 50 candidates pop up is infuriating.
something i don't understand is how are these bundling kolfags getting so many followers, at some point, you get rugged once, twice, a third time by the same bundling faggots, why do you keep following their calls?
you never stop and think "maybe i am retarded?"
Bud looks like those early AI gen pictures of people.
Ambassador Thornhill, welcome to the team. I’m proud to have such a dedicated leader join us as Ambassador-at-Large to Monitor and Combat Trafficking in Persons. Human trafficking is a grave human rights issue and a transnational crime exploiting men, women, and children for profit. We will continue to go after traffickers, protect survivors, and deliver justice for the American people.
ShaTwo56 retweeted
AI hate consistently seems to come from a... let's say... very specific venn diagram of subcultures.
Finding out the XRPL Foundation is French explains everything, no wonder their security is garbage and they suck at what they do. A decade-old overflow bug nearly printing 18.4 trillion XRP because nobody checked the math? Pure baguette engineering.
The recent XRP Ledger security fix raised a lot of questions and some misconceptions. Let's clear them up.
1. Was any XRP created?
No. XRP's supply was fixed at 100 billion when the XRP Ledger launched, and no transaction is allowed to create more. This bug was a way around that rule, and 3.4.1 fixed it 2 weeks ago.
You don't need to trust us on this. All ledger data is public, and explorers and data sites read it every day. New XRP would show up in account balances for everyone to see. There is no hidden place for XRP on the XRP Ledger, every balance is public.
We monitor the XRP Ledger 24/7 and have verified the supply throughout the history of the ledger. Others in the community verified this too, and anyone can do the same.
Transaction fees are destroyed, so the supply is deflationary. About 99.986 billion XRP exist today.
2. How did this go unnoticed, and what's next?
No normal payment comes anywhere near triggering it. It took hundreds of deliberately constructed operations.
AI makes bugs like this faster to find, for the bad guys and the good guys.
Together with RippleX and the community, we will ensure the XRP Ledger is protected against such vulnerabilities. This means radically applying Formal Verification and AI adversarial testing, collaborating closely with security researchers, and strengthening the bug bounty program.
You'll hear a lot more about this as we progress.
3. XRP Ledger decentralization at the core of this.
A public fix shows attackers where the bug is, and AI makes that fast. With a normal amendment vote, the fix would have been public for weeks before it took effect, risking network security.
As a reaction to this, the XRPL community came together, and among them the XRP Ledger Foundation, RippleX, core devs and validators formed a social consensus and agreed on a path forward that involves shipping the fix directly. Patching a live network is never trivial, so the plan was also designed to minimize disruption for everyone running on it.
We shared the build with the default UNL validators, using the contact details each one publishes in its xrp-ledger.toml file. Public binaries followed the same day, September 25.
No single party could make that call alone. Every validator and node operator chooses what software to run, and 3.4.1 only became required through a normal amendment vote with more than 80% validator support for two weeks. Protocol changes still go through amendments.
Big thanks to Cayden Liao and Veria AI for finding and reporting this responsibly, to the XRPL core developers for building and testing the fix, and to every node operator who upgraded so quickly, especially the validators.
Full report: xrpl.org/blog/2026/vulnerabi…