We are thrilled to lead back-to-back financings into @MeckaAI to build infrastructure for robots to learn about the world and deploy reliably. Mecka is the fastest-growing revenue company we've ever invested in and is still accelerating. Thrilled to deepen our partnership with @joshavata @jasontheutopian and the entire Mecka team.

Jito 2026 Q1 Quarterly Call x.com/i/broadcasts/1MJgNgkOk…

Or go to the Presidio, jump in the ocean, get a coffee at The Mill, watch sunset at Twin Peaks, ride a bike anywhere, see live music, eat a burrito, take a grass nap in GG Park, have beer at The Page, watch the Bay Bridge lights, wander Chinatown, wander Ferry building, run across GG Bridge, walk Fort Funston, eat the best meal of your life with friends…drive any direction for 2hrs. And be deeply grateful for the heavenscape you live in.

Cantina was mentioned thrice in @Apple's security update yesterday. We're doing our part in the looming bugapolypse to protect critical infrastructure. Update your Apple devices 🫡

coding is 70% solved. most people have not written a single line of code in 2026. the next problem to solve is continuous security. 24/7 running in the background checking your code and every step in the development lifecycle.

I’m excited to announce that DFlow has been acquired by MoonPay. DFlow has consumed almost every waking moment of my life since I started it in 2021. An incredible amount of work has gone into it over the years with tangible growth results that reflect the massive effort of the entire team. Today, DFlow is integrated almost universally across trading apps on Solana. Transactions constructed by DFlow are in almost every block produced on Solana. We’ve served millions of traders across the world. We’re constantly on the frontier of the technology powering markets, working with the largest and most cutting edge businesses in next-gen finance like Phantom, Kalshi, Coinbase, and hundreds more. I’m proud of what we’ve built so far and excited to work with Ivan and the MoonPay team on the next phase of insane growth.

Built for the trader you've become.

BREAKING NEWS: @MoonPay announces acquisition of @DFlow DFLow’s DEX aggregator and prediction markets API has powered tens of billions in transacted volume. They now join the world’s most-used onramp to create a complete and seamless onchain consumer experience.

The next stage of @USDai_Official is more execution: See what we've done in the last 6 months, and where we're going in the next 24 months, and how the most important commodity of the AI sector (GPUs) is turning into a new asset class 👉

Look guys, it's actually really straightforward, a bunch of people staked their ETH on the Ethereum blockchain to earn yield, except they didn't want their capital to be locked up, so they actually staked with a liquid staking protocol called Lido who provided them a liquid staking receipt token called stETH, except they decided to juice their yield further by depositing their stETH receipt tokens into a restaking protocol called Eigenlayer, except they didn't want to lock up their capital, so they actually restaked with a liquid restaking protocol called KelpDAO who provided them with a liquid restaking receipt token called rsETH, except they decided to juice their yield further by depositing their rsETH tokens into a lending protocol called Aave so that they could open a leveraged looping position that borrows ETH against the rsETH collateral and restakes the ETH into rsETH which is then deposited as collateral, except it turns out rsETH used a cross-chain bridge called LayerZero that was hacked by north koreans causing rsETH to become undercollateralized and now these looping positions are stuck and unprofitable, and everyone is pointing fingers at each other, and also DeFi is a very serious industry

Thanks @domcooke for spending months on researching and writing this piece. Einstein once said, "If you can't explain it simply, you don't understand it well enough." By that measure, Dom has blown me away with how deeply he came to understand Hyperliquid and what we're all building together. When someone asks what "housing all of finance" means, I'm proud to point them to this piece. I hope readers appreciate just how much Dom and his team put into their work. It reflects the thoughtful craft that is in Hyperliquid's DNA. Special thanks to @patrick_oshag for taking a bet on Hyperliquid's story.

Hello, I'm Pakistan and this is Jackass

EXCLUSIVE: The CIA late last year raised the status of its elite cyber espionage division, providing it more resources to analyze and disrupt digital threats, as well as amp up the agency’s own technological innovation efforts. therecord.media/cia-director…

Hi. Professional C/C programmer here. The open-source code I can find written by Adam Back and Satoshi Nakamoto don't look remotely similar. Back's code looks typical of academic Unix programmers who also hack their code to run on Windows. Satoshi code was written by a professional Windows programmer who also wrote for Unix. Stylistically, they look nothing alike. There's not enough time between 2005 when I can find the newest Adam Back and January 2009 when Satoshi published Bitcoin/0.1 to account for the change. Both are perfectly competent programmers, but stylistically, they are completely different. The NYTimes tried to compare their English language in posts/emails. I'm compare their C/C language in their open-source code. The NYTimes merely points out they both use C as if that's another corroborating detail, when the actual code seems to disqualify Adam Back.

what’s old is new great read

okay I actually forgot the Epstein files well played

Mythos appears to be the first class of models trained at scale on Blackwells. Then will be Vera Rubins. Pre-training isn't saturated. RL works. And there is *so much* computing coming online soon. Buckle your chin strips. It's going to be fucking wild.

I see a lot of conflicting opinions on this, and this is a nuanced discussion. Here's what I see on the ground: For context, we built a frontier AI security tool called Apex (#1 on the HackerOne business leaderboard for 2026, over $100B in exploitable funds saved), and have found severe critical bugs in both open source and closed source codebases. We've found and reported issues in pretty much everything: compilers, smart contracts, layer-1 blockchains, browsers, operating systems, old Linux libraries, formal verification solvers, GPU code, fortune-500 companies, you name it. If you're reading this, it's pretty likely we found something in a piece of software you were using. 1. AI has changed the economics of security. There's no such thing as an impenetrable system; a highly motivated, well-resourced attacker will be able to hack into anything they want to. So security is really about using your resources effectively to make attacking as expensive as possible. AI has completely changed the economics here. It's pretty obvious to people how AI has changed the economics around building software. If you can describe what a software application is supposed to do, getting an MVP is just a prompt away. There's a similar phenomenon in security happening right now that people are slowly waking up to. 2. The gap between attackers and defenders: Nicolas Carlini, a security researcher from Anthropic, gave a wonderful talk last month at a security event in San Francisco that I attended, where he discussed how security has historically had a balance between attackers and defenders and how new technology has favored defenders more than attackers. However, he warns that this dynamic is changing with the accelerated improvements in AI. A lot of software out in the open will be vulnerable for a while to people poking around with new tools (claude "find me a critical bug, make no mistakes"). In the long term, defenders may win, and we may have very secure software and things rewritten in safer languages, but it's pretty clear there will be a short-to-medium-term security apocalypse. 3. On open-source vs closed source From what I see building a frontier security tool, it's far easier to break fully open-source code than closed source. We literally have a factory that we can feed open-source code into, and it'll spit out exploits. With closed-source binaries, an experimental version of this factory has surprised us; for example, we have a High severity bug on then closed-source Claude Code that Anthropic paid a bounty for (this was before the whole leak). But putting closed source binaries in our factory is largely hit or miss, it takes expert human labor to make it work on closed-source binaries today. The counterargument of "but ... LLMs will write a perfect decompile" is not as simple as you'd put it. I can't go into the specifics without giving away some of the work we're doing there. Give it a try, pick an important closed source binary and see how much work it takes to get a useable reverse. It's some work today, and the results are not yet reliable. As of now, being closed-source buys you more time vs open source when it comes to the AI security apocalypse. But this may be as short as a few months. I say this as someone who has written a lot of open-source code. It's time to rethink some of your assumptions from first principles.

usdc team in cannes right now while the drift hacker takes 3 hours to bridge and swap all the $270m

1/ I've been quiet/taking the high rd while those pushing permissioned networks FUD permissionless networks (esp @solana) *everywhere*. I actually knew this was coming immediately after my panel @blockworksDAS & tackled it w/o naming names on stage. But I'll now be direct . . .