if @elonmusk paid 100% of his net worth ($1.4 trillion) as a tax it would only cover federal government spending for 77 days. this isn’t a tax problem…
Well worth a read. This is a very complex subject that impacts everyone. The time to prepare and tackle the tough questions is now.
https://t.co/1JLDcPtsfW
Introducing pump fun GO: Pay ANYONE to do ANYTHING
Create & complete bounties for ANY task and leverage the power of humans & money across the globe
The world is at your fingertips. It’s time to GO 👇
I will soon be introducing a bill to give the public a 50% ownership stake in the largest AI companies in America.
This would guarantee that the trillions created by AI are used to improve the lives of all of us — and block oligarch decisions that harm the American people.
X is killing Communities tomorrow. Today, we’re saving them.
We just launched THE permanent home for ANY crypto community on ANY chain.
Millions of eyes. No more spam. No more FUD. No more targeted bans.
Introducing Coin Communities 👇
The pump fun app just got BIGGER!
Introducing frictionless multichain trading: trade Ethereum, Base, BNB, and more on the pump fun app now
One wallet, one currency, more chains. Join now 👇
Introducing USDC pairs
Coin creators now have the option to launch with USDC-paired liquidity pools; for more stability, better coin distribution & higher ceilings.
Learn more 👇
A big move towards better onboarding of retail users and a healthier ecosystem.
Aside from introducing a stablecoin as the base currency for launched coins, the market parameters are now back to where they were during pump’s most prosperous eras.
More stability, higher floors, higher ceilings, better distribution, less supply abuse, a more balanced ecosystem.
We are investigating unauthorized access to GitHub’s internal repositories. While we currently have no evidence of impact to customer information stored outside of GitHub’s internal repositories (such as our customers’ enterprises, organizations, and repositories), we are closely monitoring our infrastructure for follow-on activity.
today is a turning point for $PUMP and pump fun
I want to give more context on the bigger picture and where we're actually going.
over the past ~9 months, 100% of revenue went into buybacks. basically no other platform in crypto has done that at this scale.
however, we received ongoing feedback specifically on the feeling of a lack of trust - in the certainty of buybacks, in what would happen to the bought-back tokens, even in whether the business itself would be here in a year.
today, we’re changing that.
it started with burning ~$370M worth of $PUMP purchases. ~36% of the circulating supply removed from circulation, forever.
but that isn’t enough. we’ve also allocated 50% of our next year of revenue to programmatic buybacks & burns. no more uncertainty for those who believe in us & those we’re proud to call our community.
but why not 100%? the short answer is the business simply needs the other 50% to grow.
a large treasury gives us the flexibility to make big bets over the next 5-10 years, and 50% of ongoing revenue enables us to build better products, infrastructure & reinvest into the ecosystem. I am extremely confident that 50% of the business we're building toward will dwarf 100% of the business we have today.
🚨 BREAKING: Wiz Research discovered Remote Code Execution on https://t.co/SvN2lGsnbO with a single git push
The flaw in @github allowed unauthorized access to millions of repositories belonging to other users and organizations 🤯
10h ago @litecoin experienced a coordinated attack on the chain that resulted in 13 blocks reorg that took more than 3h to generate.
During this time attackers were performing double spend attacks on multiple cross-chain swapping protocols.
We are investigating the situation.
🚨 New findings in our @Checkmarx compromise investigation:
- VS Code / Open VSX extensions delivered a second-stage payload as mcpAddon.js
- It was silently downloaded from a hardcoded GitHub URL pinned to a specific commit in Checkmarx’s own repo
- It was executed via Bun
- The malware harvested GitHub, AWS, Azure, GCP, npm, SSH, env vars, and MCP-related credentials
- Stolen GitHub tokens were used to create public repos for staging exfiltrated data
- The malware injected malicious GitHub Actions workflows to capture repository secrets
- Stolen npm credentials were used to identify writable packages for downstream propagation
- TeamPCP appears to be taking credit publicly