Announcing Pico Prism, the state-of-the-art zkVM for Ethereum real-time proving. 99.6% of blocks proven under 12 seconds, 6.9s average with 64 RTX 5090 GPUs. This marks a major step toward scaling Ethereum by 100x and a future where you can validate the chain from a phone.

This week the photobook of Masaki Sato "prism" has been released： Digest： English Guide： #佐藤優樹# #satomasaki#

Former SpaceX astronaut Garrett Reisman reveals the single prism Elon Musk runs every major decision through "He measures pretty much every major decision by whether or not it brings the day when we have a self-sustainable colony on Mars sooner or later" "That's the prism by which he makes every single decision he makes" "He's got an idea and he'll keep pushing, and he gives us aggressive timelines that we have to work to" "We work really hard to try to meet them. It's hard when you're doing stuff that's this complicated to predict exactly how long it's going to take" "We end up falling a little bit behind, but we do our best"

We shared a bit of the engineering work behind Pico Prism at @EthCC in Cannes. 🇫🇷 We walked through some of the technical work that let us reduce Pico Prism's GPU footprint from 64 to 16 with no noticeable performance regression. Let's listen in:

MegaETH Economics Note 1 I want to start offering informal notes on the MegaETH economy so people can get a high-level view of what is going on. Please note all figures, tables, graphs, and commentary should be considered preliminary and not to be relied upon (including resolution of prediction markets). Since I wrote on the topic earlier, let’s kick off with an update on the USDM money supply. Full definitions of M0, M1, and M2 are at the bottom. We will ignore M3, since it isn’t relevant for now. April 30, 2026 (TGE Day) M0: ~60 million M1: ~360 million M2: N/A May 15, 2026 (Today) M0: ~51 million M1: ~653 million M2: N/A What we see so far is that USDM supply is overwhelmingly concentrated in Aave. Most of the M0 supply is in DEXes, serving as liquidity primarily on Kumbaya, World Markets, and Prism, in that order. The fall in M0 is appears to be driven by reduced LPing on those protocols, while the M1 supply grew quickly before leveling off at its current level. The main observed demand drivers look like looping USDe and for using USDM as a funding currency, since it can easily be converted to USDC and used to refinance higher-rate debt on other chains. Both appear to be at an equilibrium at the moment. I hesitate to make predictions, but if I were, I would expect M1 to consolidate around here until Aave or another lending protocol provide other offerings that would increase M1. There have been no collateral asset additions to Aave since USDe, and the rate environment on other chains has been settling down, reducing the demand to refinance foreign USDC debt into domestic USDM debt. It’s still early days on MegaETH, so as more apps come online - in particular DeFi apps - I would expect considerable movements in both M0 and M1 supply. It will take deployment of a protocol with time deposits before we begin to see any real difference between M2 and M1. M2 showing up will mean a structured credit market is beginning to develop. I’ll close by noting that the core strengths of MegaETH’s app portfolio at launch have been consumer-facing financial entertainment apps that don’t directly impact the USDM money supply, but increase the velocity of USDM. Given the unexpectedly large monetary base of USDM out of the starting gate, it won’t make discussion of the *overall* USDM velocity of money very high, but are producing legitimate MegaETH GDP. I’ll try to track GDP directly as it grows in relation to the monetary base. Definitions: M0 consists of USDM held by the public outside of deposit-taking protocols, centralized exchanges, and companies M1 consists of 1) M0, 2) demand deposits denominated in USDM at deposit-taking protocols, centralized exchanges, and companies, and (3) other liquid deposits, consisting of Other Checkable Deposits and savings deposits (including money market deposit accounts) M2 consists of (1) M1, (2) time deposits and maturing assets (<6 months) denominated in USDM

I am the Senior Vice President of Workforce Architecture at Cloudflare and I need to tell you about the best decision this company has ever made. We posted $639.8 million in quarterly revenue. 34% year-over-year growth. Record net retention. The strongest quarter since IPO. And then we fired 1,100 people. Not because of the quarter. During the quarter. I need you to understand the sequence because the sequence is the whole point. My team built the model that made this possible. We call it CIRRUS: "Capacity-Indexed Reduction and Reallocation for Upside Scaling". CIRRUS took our revenue trajectory, our margin targets, and our board's stated appetite for what they called "structural boldness," and it determined that the optimal time to execute a 20% headcount reduction is at the exact moment of peak financial performance. Not during a downturn. Not during a miss. During a beat. The logic is simple. When revenue is surging, the market reads a cost reduction as discipline. When revenue is falling, the market reads the same reduction as panic. Same action. Same 1,100 people. Completely different stock reaction. CIRRUS identified a seven-day window where the earnings momentum and the layoff announcement would compound rather than cancel. I found the math beautiful. I still do. We deactivated 1,100 badges between 9:00 and 9:04 AM Pacific on a Monday. People Analytics determined this was the four-minute window of lowest Slack activity. We called it a "clean cutover." Someone in Infrastructure suggested "zero-downtime deprecation" but Legal thought it sounded too much like a product feature. I thought it sounded exactly like a product feature, which is why I liked it. But I deferred to Legal. I always defer to Legal. That is one of the things that makes me good at this job. The people we cut were not underperformers. I want to be very clear about that because clarity is a Cloudflare value. Sixty-two percent had received exceeds-expectations in their most recent review cycle. Fourteen had been promoted in Q3. One engineer in our Austin office — I'll call him Marcus, though that is not his name and the reason I'm not using his name is not that I've forgotten it — had shipped the caching optimization that directly contributed to $14 million in new enterprise contracts. His manager nominated him for the Raygun Award, which is our internal recognition for outsized impact, six days before I added him to the CIRRUS list. He won the award on Wednesday. His access was revoked the following Monday. The ceremony and the termination were planned by different teams in the same building and neither team knew about the other. I don't think this is ironic. I think this is how large organizations work. The left hand builds. The right hand optimizes. Both hands are attached to the same body and the body is performing well. We let Marcus keep the trophy. It's a small acrylic prism etched with a lightning bolt. It costs us about eleven dollars. His annual cost-to-company was $312,000. CIRRUS selected the 1,100 based on three variables. I'm going to share them because I believe in the methodology. First: salary band. Employees in bands 6 through 8 offered the highest savings-to-replacement-risk ratio. Second: visa dependency. Employees on sponsored visas have a 60-day window to find new employment or begin departure proceedings. This creates what CIRRUS categorizes as "low-friction separation" — the compliance timeline is externally enforced, which reduces our administrative burden. I presented this variable to HR and they requested I rename it from "visa dependency" to "mobility factor" in all future documentation. I agreed. The math didn't change. Third: managerial tenure. Employees whose direct manager had been at the company less than eighteen months were 73% less likely to generate a negative Glassdoor review, because the manager-employee bond hadn't fully formed. CIRRUS weighted this at 15% of the selection score. We call it the "attachment coefficient." We told the market the layoffs were an AI workforce pivot. We said artificial intelligence was making certain roles redundant. We said we were reallocating resources toward our AI gateway products. This was a communications strategy. Not a workforce strategy. The AI framing was my team's recommendation and I'm proud of it because it worked. Two analysts upgraded us the same week. The stock moved 8% in five sessions. The entire AI narrative was four paragraphs in a press release that took my comms partner and me an afternoon to write. Four paragraphs. 1,100 people. 8%. I don't know what the per-paragraph return on that is but I think about it sometimes. The actual AI initiative employs thirty-seven people. We cut 1,100 to fund 37. The ratio is not in any of our public materials. There is a Slack channel called #bright-futures# that our Head of People Experience created for the remaining employees. It posts an automated message every morning at 8:45 AM: "You are the ones we chose to keep." The message includes a rotating motivational quote. Last Tuesday it was a Winston Churchill quote about perseverance. The channel has a custom emoji called :survivor: that the Culture team designed. It's a small cartoon phoenix. Nine hundred people have used it unironically. I find this genuinely moving. I think it shows resilience. My wife says it shows something else but she works in education and I think the frameworks are different. The severance was calculated using a model we licensed from the same consulting firm that built our customer pricing tiers. Median payout: eleven weeks. We benchmarked against industry and landed at the 50th percentile exactly, which our CHRO described as "fair by design." The 1,100 will burn through their severance while our stock price digests a 20% cost reduction applied to a revenue base that was already growing 34%. By the time the last check clears, the savings will have funded the first full quarter of the AI initiative. The one with thirty-seven people. My performance review is next month. I've been told informally that I'm on the COO track. The criteria include "demonstrated ability to execute at scale with minimal organizational disruption." The 1,100 people are the execution. The stock price is the scale. The four-minute badge window is the minimal disruption. I meet all three criteria. I designed all three criteria. Not the review criteria. The outcomes. I keep the CIRRUS model on my laptop in a folder called "Workforce Planning FY26." It sits next to a subfolder called "Offsite Photos — Maui" from the leadership retreat we took in January, where we set the annual targets that the 1,100 people spent four months hitting before we terminated them for hitting them. Marcus's desk in Austin has been reassigned. I don't know to whom. The acrylic prism is probably in a box somewhere. Or maybe whoever cleaned out the desk kept it. It catches the light nicely. I noticed that once, when I visited the Austin office to present the CIRRUS methodology to the regional leadership team. They gave me a standing ovation. The prism was on a desk near the back of the room, refracting a small rainbow onto the wall behind me. I didn't mention it. I stayed on my slides. I'm proud of the work we've done here. I think when people look back at this quarter, they'll see it as the moment Cloudflare became a different kind of company. I think they'll be right. I think the 1,100 people would agree, if you explained the math to them carefully enough.