BOYNEXTDOOR 4th EP [No Genre] Track Spoiler: Sound Tour 🔗 #BOYNEXTDOOR# #보이넥스트도어# #BND# #No_Genre# #I_Feel_Good# #BOYNEXTDOOR_123_78# #Step_By_Step# #장난쳐# #Next_Mistake# #오늘만_I_LOVE_YOU#

Why Generic Humanoid Robots Will Fail — And What's Next Imagine an alternate world where we never invented the car. In that world, a robotics engineer might reasonably conclude that robotic horses are the future — replace the living ones, keep the stables and saddles, ride them to work. Convenient, modern, and the roads stay free of manure. It sounds absurd only because you already know about cars. We keep making the same mistake with humanoid robots. Consider transportation. To finally make driving safe, we had two options: put a humanoid in the driver's seat, or embed sensing and compute directly into the vehicle. Waymo chose the latter. It has no steering wheel. It exists purely to move people efficiently from A to B. The humanoid was not needed. Consider a sock factory. Yes, you could replace workers with humanoid robots one-for-one on the assembly line — and gain maybe 2-3x efficiency. Or you could completely redesign the workflow around a purpose-built autonomous sewing system and eliminate most of the factory, the chairs, the cafeteria, the manual sewing machines, the HVAC, the doors, and the restrooms. The actual optimization is to side-step the previous human-imposed physical constraint. Look at Ukraine. The front lines aren't filling up with Terminator-style humanoids carrying rifles. Human soldiers are being replaced by heterogeneous swarms of purpose-specific drones: some for reconnaissance, some for logistics, some for delivering munitions. War is being restructured around the desired outcome (survival), not the soldier's shape. Consider a 1970's office. Want to move information through teams of people? We once used typists, paper, trucks to supply the paper, typewriters, and repair technicians. A linear improvement would have been to replace the human typist with a 10-fingered humanoid. What actually happened? The entire workflow — paper, printers, typewriter factories, delivery trucks, the desks, the offices — was obliterated. Email deleted the human clerk's entire universe. Consider cancer early detection by mammography. Today, getting a mammogram requires expensive hardware, logistics infrastructure, human nurses and doctors, a biopsy workflow, a human pathologist with a microscope (imported from Germany or Japan), a written finding, multiple physician reviews. Sure, you could replace the pathologist with a humanoid (the microscope focus knob requires finger dexterity) and get a modest efficiency gain (and faster responses at 2 am). Or — the far more likely future — we all swallow a cancer detection pill every few months, and 24 hours later a color-changing sticker on our arm turns red or green. No hardware. No hospital. No logistics. No pathologist. No office. No desk. No humanoid. The workflow isn't optimized by a literal drop-in swap of a human pathologist for a humanoid. The entire workflow simply ceases to exist. Consider life sciences research and drug development. We're seeing excitement about robot arms and humanoids pipetting water in research labs. Robot horses, episode 7. We don't design aircraft by crashing test planes — we simulate them entirely in software first. Biology will go the same way. The path to scalable drug discovery isn't robot arms in conventional wet labs demonstrating 10 fingered prowess in manipulating Eppendorf tubes filled with purple food coloring. Rather, we need in-silico biological models that evaluate billions of hypotheses computationally, with physical manipulation of atoms only at the very end. The clear pattern. Efficient automation doesn't try to replicate a 10-fingered human in a static context. Automation eliminates physical rate-limiting steps in their entirety. That's why "classical" humanoid robots, as a generic category, will largely fail. They're robotic horses. They assume the infrastructure and workflows stay fixed and only the 10-fingered human is swapped out. That's not how economic and technological pressure works. What actually matters? If humans continue to inhabit the physical world, then moving atoms will remain important, and that requires five things: atoms, energy, force generation and actuation, sensing, and compute. Everything else — form factor, number of limbs, type of end effector — is a variable to be optimized for the task. So if you are a pathologist, a robotics engineer, a teacher, a parent, a politician, or a sewing factory owner - please think different. Most obviously, we should all anticipate, and build for, a future in which robots exhibit extreme physical fluidity: Two arms or four. Wheels or legs. Tentacles or flippers. Three fingers or twelve, or none at all. Eyes at the front, side, or tip of a tentacle. At OpenMind, we don't care what you look like right now - we got you, in all your physical form factors. OM2 ships in July, for all machines. Let's build.

There was a time in my career when my world revolved around going after the worst pimps and human traffickers abusing young women and children. For years, nothing else mattered except holding those responsible to account. Along the way, I lost relationships. I made mistakes. No one came before the mission. You try to influence the next generation of investigators to carry the work forward and do better than you did. After many years, I needed to step away psychologically. If you have ever pushed human trafficking cases through the courts, watched survivors and young people testify, and watched them be cross examined in ways that can feel cruel and devastating, you understand the impact it has on you as a police officer and as a human being. It is one area of policing that changes you forever. All police officers carry heaviness. All people do. Police leaders are no different. A few nights ago, my good friend and I grabbed late night Asian food. Just a regular cowboy and a typical Asian guy in jeans and T shirts testing our spice levels late at night. Without even realizing the impact, @paulbrandt challenged me to step back into the fight in a different way. The mental break was over. Thank you, Paul, for everything you continue to do for survivors and vulnerable people across this country. You have my commitment. And I am fortunate to have an incredible team of investigators in London carrying this work forward every day. Stay tuned. #MentalHealthAwarenessMonth# #humantrafficking# #NotInMyCity#

Today we're announcing two product changes for organizing communities on X: 1. XChat now supports joinable links for groupchats. Create a public link & share direct to Timeline. With support for 350 members per chat (and growing), Groupchat Links are the fastest way to bring people together on X. 2. Due to declining usage, we're deprecating X Communities on May 6. To migrate your Community's members, pin your groupchat link so people can join it over the next 2 weeks. This is part of our broader effort to simplify the experience on X. Make no mistake: we are investing heavily in niche communities with the launch of Custom Timelines—and much more to come.

£3.3 billion lost in a single day. $1 billion made by one trader Bookmark this BBC documentary - it shows the cleanest case of overreaction bias ever caught on tape. One sentence triggered it. But the real reason it cost £3.3 billion was what the British government did next September 16, 1992. The British pound was pegged to the Deutschmark inside the European Exchange Rate Mechanism. The peg was already cracking. Then Helmut Schlesinger, president of the Bundesbank, gave an interview he believed was off-the-record. One sentence hinted that more currencies might need to devalue. A journalist published it. Within hours, every trader in London was selling pounds That was the trigger. The collapse was the response The British government decided to defend the pound by raising interest rates from 10% to 12%. The market read it as panic. They raised again - to 15% in a single afternoon. The market read it as desperation. Soros' fund stopped selling in £5 million lots and started selling in £100 million blocks. One trader inside the fund called it "an invitation to double up." This is overreaction bias on a national scale. Not one mistake but two layers stacked - the government underreacted to market signals for two years, then panicked when reality hit. The harder they pushed, the more obvious it became that they had already lost By 8pm the pound was out of the ERM. Bank of England had burned £3.3 billion in reserves. Soros had made $1 billion in a single afternoon. The Chancellor went home, opened a bottle of white wine, and slept peacefully for the first time in months The lesson sits in every market today. The crowd doesn't price danger in proportion - it ignores it, then overcorrects, then overcorrects the overcorrection. The people who make money read the second move before it happens "Overreaction" is one of 5 cognitive biases I broke down in my article ↓

Intel CEO Lip-Bu Tan sat down with CNBC’s Jim Cramer to talk about Apple; Intel 14A rivaling TSMC's top chip production technology; Shortages of CPUs and substrates; and the state of Intel's turnaround. How to know when Intel signs Apple or other foundry customers: Intel CEO Lip-Bu Tan: “Over time, the IP will be ready so we can serve some of these customers. I think the best indication, when you see I increase my capex, I’m putting money to buy equipment, that means I have real customers. That’s the discipline I have.” Intel 14A manufacturing process and EMIB-T advanced packaging: Intel CEO: “(A14) is 1.4nm, this is the most advanced. To be candid with you, in 2028 we will have risk production. 2029 will be volume production. It will be the same time as TSMC. So that is a major, major breakthrough, and I’m so excited. And we already have multiple customers engaged with us, and we have 0.5 PDK available.” Taking advantage of TSMC’s CoWoS shortage Intel CEO: “Our technology is called EMIB-T, this is the next generation of advanced packaging. We really have the best technology and now we are making sure we can bring it into volume production with reliable yield so the customer can count on us.” CEO: “You know, CoWoS…(TSMC) ran out of capacity, so in a way we’ve become in the unique position to support that and that’s something we are very excited (about).” Shortages of CPUs and Substrates CEO on the CPU shortage: “I’ll give you one example. I had one customer say Lip Bu, we gave you the forecast for this year, but we want to increase 3x, and I say I cannot do it overnight but give me a few quarters and I will catch up. So, I think this demand is not short term, it’s the next couple of years. It’s a great opportunity.” CEO: “Right now, as I mentioned, CPU is in high demand. And that’s good for me. I cannot even ship enough to the customer. It used to be the CPU to GPU ratio for training was 1-to-8. And now, because of inference and agentic AI, and more agents you have to manage, and orchestration, and reinforced learning, CPU is actually better, so that becomes 1-to-4 and 1-to-1 and some people even talk about 4-to1, and so that’s a huge opportunity to me to drive the CPU....” CEO on Substrates: “A couple of customers have prepaid for substrates, because the substrate supply chain is very tight – so I need to put up the money to secure this material…(and it shows) the commitment to me – so that’s very exciting.” Intel’s Turnaround CEO: “We used to have leadership in data center, and over the years we lost it…We made some big mistakes,” he said, adding he’s brought back some talent to refocus the product lines and that “Coral Rapids will have multi-threading, and will come out very strong.” CEO: “When I took over, the 18A yield was not good, so I had to ask some of the ecosystem partners to help me look at the data, see how to improve. The best practice is to see 7% or 8% yield improvement per month, and now I’m seeing it.” CEO: “The other part is supposed to be the yield performance, defect density, you know at the end of the year to see the target. Now I see that even before the end of the year – so that is very big encouragement for me and also that’s why Panther Lake can be shipped in volume now. And now some customers knock on my door and say Lip Bu, now we hear you are making great progress, can you now open up to outside customers? So that is very exciting. It’s a lot of hard work, it’s a lot of teamwork, it’s a lot of talent I’ve brought on board.” CEO: “In the past we made a lot of mistakes and now we correct the mistake and we’ve simplified the roadmap. By the way, from Day 1 I came on board as the CEO, I have all the engineers report to me so I have an understanding, hear from the customer, and know where are the mistakes.” Cramer: “They didn’t report to the previous CEO?” CEO: “No. And in a way, they had too many silos, too many people reporting…So I decided, the best thing is to really understand where the problem is, so I can focus on the engineering, how to redesign, simplify the product and then get the real killer products out.” Cramer asks about China, Taiwan and the importance of US manufacturing: CEO: “I was very glad for President Trump understanding the strategic importance for the United States to have (chip manufacturing supply chain) and their support is so valuable to me – it’s so critical for the country to have the technology, R&D development, manufacturing in the United States. That’s why I came back in, as a U.S. citizen – as a calling – to do that.” CEO: “From time to time I update President Trump and also (Sec.) Howard Lutnick and they are big supporters of me and we are delighted to have their support.” Going forward: CEO: “I recruited some key talent…and now, by the end of June, I will have my team, what I consider my team, so that we can work on the next 5-years, 10-years, how to become a different company. I call it the New Intel, work at the speed of light, work as a team to progress forward.” $INTC $TSM #Samsung# $UMC $GFS #semiconductors#

Dear ICP community, the Internet Computer has now been running strong for 5 years 👏👏👏 Here is a celebratory preview of ICP "cloud engines," the sovereign frontier cloud technology the network shall soon provide from Main points: — Cloud engines enable anyone to spin up their own sovereign frontier cloud. The technology involves an extraordinary inventive step, in which cloud is created from a mathematically secure network of nodes. The nodes run as part of the Internet Computer network ( but are selected and configured by the cloud engine's owner. — The frontier cloud provided by engines is strongly focused on enabling AI agents to build and update online applications and services for us. The world is changing fast, and nearly all new online apps and services are already being built with the help of AI, and thus cloud engines target the future of cloud. — Software hosted on cloud engines is tamperproof, which means that it is immune to infrastructure hacks, because it runs inside a mathematically secure network protocol, rather than on computers directly. This means that AI agents, and those building with them, don't need to have a security team in the loop, or to trust someone else's security team. This is crucial, because in the future, non technical people will demand the freedom to build with full automation — where they just need to issue instructions to AI about what to build, and don't need to worry about anything or anyone else. Of course, apps and services running on engines are also vastly safer from the new breed of hacker being enabled by frontier AI. (The cloud engines themselves are also "tamperproof." Even if a hacker gains physical access to some portion of a cloud engine's nodes, and can make arbitrary changes, the computations and data of the hosted apps and services cannot be corrupted or interrupted so long as the network's fault bounds aren't exceeded. The recent hack of Vercel, a major cloud platform, which gave hackers access to the apps it hosted, provides additional perspective on the importance of this advantage.) — Software hosted on cloud engines is guaranteed to run, so long as a sufficient number of the engine's nodes are running. This means that AI can build applications and services without the need to have a human systems admin team constantly tinkering with the underlying platform to keep it running, which is again crucial, because in the future, non technical people will expect the freedom to use AI to build without the support of others. — New frontier programming language technology, in the form of the Motoko language developed by Caffeine Labs, leverages seminal "orthogonal persistence" technology that unifies program logic and data to deliver further unlocks for AI (Motoko is the first computer language being developed that targets agents that are writing software rather than humans engineers per se). Nowadays, AI can build and update production apps at a prodigious rate, even at the speed of conversation. But it can also make mistakes, and there's a risk that an update it creates might be "lossy" in the sense it causes some transformed data to be lost. Again, in this new world, it's both undesirable and impractical for everyone to have to have a systems admin team on-hand to detect lossy updates and roll them back, but Motoko provides a solution: it can detect new software updates are lossy before they are applied, reducing potentially catastrophic errors by AI to harmless coding retries. — Software hosted on cloud engines is "serverless" but unlike traditional serverless software, directly it directly incorporates data through "orthogonal persistence." Another key purpose is simplify backend software logic and fuel the modeling power of AI by increasing abstraction (sorry for the technical language!!!). Put simply, this enables AI to produce more sophisticated backends, faster, and at dramatically lower costs, as measured by the number AI API tokens consumed during coding. (Tip for the technical: orthogonal persistence is a new paradigm where "the program is the database," and data lives inside program variables, which is possible because it's as if hosted software runs forever in persistent memory). — An expanding database of skills at shall make it possible to develop and directly deploy apps and services to your cloud engines directly from Claude Code, Perplexity, Codex and other AI platforms. Further, your account on can be connected, so that new apps and updates created through conversation automatically appear hosted from your cloud engine. In the future, R&D is going to be very seamless. You converse with AI, and your secure and unstoppable apps or services are created or updated. Cloud engines are designed to directly support this "self-writing cloud" future where we can work hands-free. — Tech sovereignty is becoming a huge issue worldwide, with governments and corporations seeking to create sovereign tech stacks owing to geopolitical tensions. Increasingly, people are realizing that tech provided by foreign nations can come with hidden backdoors and kills switches, from the base platform, right up through hosted apps and services. ICP technology is open source, and those building on ICP using AI own their own source code. When you have the source code, you can verify that there are no backdoors, and when you own the source code thanks to AI, you can update it at will, freeing you from vendor lock-in. But cloud engines take sovereignty much further... — You create a cloud engine by selecting the nodes that will be combined. You can choose the class of nodes used, and their number, but more importantly, you can choose who operates the nodes, and where they are located. Almost any configuration is possible, because the Internet Computer scales the security privileges afforded to hosted software within the network according to configuration (software hosted on cloud engines can directly interoperate with software on other engines and traditional subnets, but base restrictions are applied according to security rules). A cloud engine can be created within a region such as Europe, to comply with regs such as GDPR, or completely within a sovereign state like Switzerland or Pakistan. But cloud engines go further still... — Sovereignty is also about freedom from vendor lock-in. Cloud engines are essentially ICP (Internet Computer Protocol) network configurations, and this means the underlying compute nodes they combine can be swapped out without interrupting their hosted apps and services. This is a big deal. In addition, cloud engines now support nodes that are instances running on Big Tech's clouds, in addition to nodes that are dedicated specialized hardware, as per the Gen I and Gen II nodes that dominate the Internet Computer today. For example, it is possible to have an engine running across different AWS data centers, say, and then reconfigure the engine to run across a mixture of AWS, Google, Azure and Hetzner for even more resilience, without the users of hosted apps and services noticing a thing. That's true freedom. — Sovereign AI is becoming increasingly important too, and cloud engines allow special "AI nodes" to be added to them, so that hosted software can perform inference on hardware provisioned by the owner from a location the owner has selected. Even though the AI nodes are only accessible within the cloud engine, they can still benefit from the forthcoming Internet Intelligence Gateway (IG), which will make it possible to validate inference performed on key frontier open weights LLMs, even when the inference is performed on completely independent AI clouds. When the results of inference are received, this technology can verify that neither the prompt+context (input) nor the inference result (output) have been modified, and that the results were produced by the precise LLM expected. This ensures that AI clouds don't cheat by running inference on cheaper models than are being paid for, and bad actors aren't modifying the inputs or outputs to surreptitiously insert advertising into results, say, or change facts, or insert malware when code is being generated. What's super cool about this technology is the cost of the verification is scalable. A very valuable additional security can be achieved with only 1-2% of extra cost. — Scaling apps and services when they hit capacity limits is another thorny problem that cloud engines help the world address. Engines make scaling possible without rewriting or reconfiguring software. The query workload capacity of hosted software can be horizontally scaled simply by adding new nodes to an engine, and nodes can also be added in geographical proximity to demand. Meanwhile, update workload capacity can first be scaled-up by swapping an engine's nodes out for the next class up, and then when no larger class of node is available, horizontally scaled-out by "splitting" the engine into two, which doubles available capacity. (Technical tip: horizontally scaling update capacity by splitting engines requires multi-canister architectures). — For those who have been following how Caffeine builds apps that can efficiently store large numbers of files, I should mention that apps built on cloud engines will also support the new ICP Blob Storage cloud network (since cloud engines currently have up to about 3 TB of memory, which apps storing large amounts of files can easily exceed). We are also working on allowing blob storage nodes to be added to cloud engines, to enable sovereign mass blob storage within an engine, similarly to how AI nodes can be added currently. — Lastly, but certainly not least, I should mention that cloud engines are multi-blockchain capable, and ready for digital assets, thanks to the clever math at their core. For example, an e-commerce service built on a cloud engine can securely accept and custody stablecoin payments, or a multi-chain DEX could be hosted. Further, engines can support software autonomy (software orchestrated and controlled by other autonomous software, in a decentralized way) and can themselves be orchestrated by SNS technology, and thus run autonomously too. Today, though, the focus is on *mainstream* cloud. This year, the cloud industry will generate approximately one trillion dollars in revenue. That number is already huge, but is expected to grow to two trillion dollars by 2030. After years of continuous development, which have seen more than $500m spent on R&D, the Internet Computer network is now tacking directly toward this mainstream cloud market with cloud engine technology. In their first version, cloud engines are not meant to be a cloud panacea. For example, currently they are not ideal for working with big data. You should use something like DataBricks for that. Cloud engines are carefully targeted at enabling AI to produce traditional online applications and services, including SaaS, in a safer and more productive way, which represents a new market segment with tremendous potential. Of course, DFINITY will continue to work relentlessly to push forward ICP's capabilities, so expect further developments. It's worth mentioning that this cloud segment isn't just about creating new apps and services using AI, it's also about replacing legacy systems and apps built on super expensive SaaS services. Caffeine Labs is working to produce technology (Caffeine Snorkel) that can study an enterprise's legacy systems and app built on SaaS, create replacement systems and apps, and migrate the data, while supporting key stakeholders through the process over email and chat, with full automation. Thus the legacy systems and SaaS markets shall also be addressed by cloud engines. Zooming out, and reasoning in a more metaphysical way, we believe, as we always have, that there is room for a new kind of cloud created by mathematical networks, that provides seminal advances in the fields of security and resilience, as well as true sovereignty and freedom from lock-in. That this same technology, with the help of additional technologies like orthogonal persistence and Motoko, enables AI to build for us without the need for so much oversight, and to create more backend sophistication while consuming fewer AI API tokens, enables ICP to bring game-changing advances to the world. Cloud engines will work synergistically with the Intelligence Gateway, which will enable apps and services running on engines to seamlessly leverage AI, wherever that AI is running, while providing verifiability at extremely low cost for open weights frontier models. We believe that cloud engines represent an inflection point in the storied history of the Internet Computer project, and I'm very proud to be sharing the details with you on the network's fifth birthday 💪 I'll be back with more news soon!!

Some of my perspective on where the @ethereumfndn is going. First of all, this is only my own view. The board is not just me, and I have no extra special powers on the board that the other board members do not. @aerugoettinea is the one executing much of this transition. My input has been largely on technical questions. The board is in the process of expanding, and my own power within the org will continue to decrease, which is honestly what I want. The 2025 era brought many important improvements to EF and its ability to execute. Many issues were resolved, and EF continues to benefit from its improved efficiency and greater focus on concrete goals to this day. And so with those problems resolved, early this year, the largest remaining hole that I perceived was something different nagging at me: I would regularly spot people saying things like "vitalik says these beautiful things about ethereum needing to be decentralized, and have privacy, and be a sanctuary technology, but why do the EF's actions not reflect that?" Now, you may have been hearing something different. You may not have been sensing a feeling of crisis at all, and maybe were hearing people saying that finally we were taking execution and BD seriously and the main task for us is to keep going that way and be even better and faster. Then probably there is genuine difference between you and me, in what kinds of criticism I take most seriously, and what kinds of critics through their criticism are most able to make me feel pain. As an analogy, let's briefly switch over to a different domain. One belief you can have about Google is that it is a success story, and has brought a lot of good to humanity in organizing the world's information. Another belief you can have about Google is that they had a beautiful idealistic beginning, but at some point the corruption of mainstream corporate attitudes seeped in, and they slowly bit by bit completely abandoned the "don't be evil" slogan. My belief on Google specifically is probably somewhere between the two. BUT, if you had taken me back in time to ~2008, and offered me a button to press to make Google one or two standard deviations more "dogmatic", eg. give Richard Stallman permanent veto power over some key policies, I would immediately press it. Why? Because a choice for one company is not a choice for the world, or even one country. Google existed and exists in the context of a technology industry generally drifting away from early idealistic don't-be-evil roots and toward greed for financial gain, totalizing visions of accelerated superintelligence, infiltration by sociopaths, and craven capitulation to (or worse, active participation in) government pressure for ideological control, surveillance and war. And so *one company* doing something different, positioning itself to be what George Bernard Shaw calls the Unreasonable Man, resisting the trend of the times, would have been better for freedom, balance of power and stability of society as a whole, than *all* large companies bending to dominant trends. This is a part of my version of pluralism. This line of thinking is not just mine, but I also is not too far off from what Aya and others had in mind with the Mandate. Now how does this all get to the role of the EF? EF is not a "center of Ethereum", rather EF is "one node, with a defined purpose, alongside other nodes". We've always said that the EF should be the latter, but many in the Ethereum ecosystem (and even within the EF) wanted us to be the former. Now, we are taking action to ensure that we will be the latter. This is particularly important because EF is a limited organization, with limited resources and limited organizational capacity. The EF has only ~0.16% of all ETH (less than many other individual ETH holders), whereas among other blockchains it's common for "the central foundation" to have 10-50%. Fiscally, the EF was originally designed to fulfill a limited work scope defined in the token sale docs and other pre-launch materials (building the chain software; getting through Frontier, Homestead, Metropolis, Serenity), which was fully completed in 2022; it was not designed to be an eternal steward. And so today, the EF is choosing to use its remaining resources to pursue longevity over breadth (yes, this means we sell less ETH). The EF focuses *specifically* on those activities critical to the success of ethereum as a censorship/capture-resistant, open, private and secure system, that would not happen otherwise. This means making hard choices, and in some cases even activities that we highly approve of and people that we highly respect becoming outside of the EF. People of great technical talent, public respect and even alignment with the mission and CROPS being outside of the EF is in fact necessary if we want important tasks to be able to attract outside capital. This also means the EF taking opinionated stands culturally. This is all intended in cooperation with all other parts of ethereum. We recognize that many other parts of the ethereum world highly respect CROPS and related values. But highly respecting is not the same as choosing to specialize and totally dedicate to a domain (Compare in a different domain: I think reducing animal cruelty is important, and I like vegan food, but am not full unconditional vegan myself) EF is still in a transition period, and we expect its new long-term form to stabilize over the next few months. What are the guiding principles of this new form? Again, I am only one person, but I can give my answer from a technical perspective (there are also critical non-technical aspects). At the core, *Ethereum must be impressive*. We are living in an age of highly intelligent AI and all kinds of other technological acceleration. "Status quo EVM, with a hard fork or two a year to optimize for short-term needs of users" is not interesting. To some, "impressive" means: 250ms latency and 1M TPS. I think Ethereum trying to go that route is a mistake. Being as fast and as scalable as possible, and only a small epsilon more decentralized than the others, is a route to mediocrity, and if we try it we will lose. I think Ethereum should scale. But I think Ethereum should strive the hardest to be deeply impressive in a different dimension: the CROPS dimension. This means things like: * Provably bug-free Ethereum. This is a goal that all cybersecurity researchers would have thought is absurd and impossible, up until roughly 6 months ago. Now, it's on the cusp of being possible, thanks to AI-assisted formal verification. So we should be frontrunners in doing this. * Available chain consensus. Ethereum is, and with lean consensus will cotninue to be, the ONLY chain that has both (i) traditional-BFT style properties that it's safe under asynchrony up to a high level of fault tolerance, and (ii) the bitcoin PoW-style property that under synchrony it's safe up to 49% attackers. As far as I can tell, literally no other chain has this or is planning for it; bitcoin goes for (ii) only and most other chains go for (i) only. Some will remember I fought hard for this, Unreasonably insisting that it is not OK for ethereum to rely on social consensus and hard forks to rescue ethereum from 34% of nodes going offline. It's OK for chains like hyperledger, bnb, solana, tempo, etc. It's not OK for bitcoin or ethereum or eg. zcash. * Intermediary minimization. The fact that smart contract wallets, protocols like railgun, etc have to send transactions through intermediaries to get included onchain is honestly embarrassing, and it's a constant point of fragility. Hence the work on FOCIL and EIP-8141 (and 7701 and years of work before) to make transaction sending intermediary-minimized with public mempool and strong inclusion properties, in a truly general-purpose way, that covers not just eg. secp256r1, but also privacy protocols and much more. Kohaku is pushing intermediary minimization at the user layer, pulling Ethereum away from the dystopian status quo world where our wallets don't even verify the chain, send our private data out to a dozen third-party servers, and toward a brighter CROPS future. Some of these goals are Unreasonable - maybe Ethereum would be "fine" getting only 50% of the way - what if we depend on intermediaries, but make it easy to switch? But going 50% of the way would not make Ethereum Deeply Impressive in the CROPS way. So we push for 100%. Fortunately all these goals are compatible with high TPS, this is a major focus of research (esp. on scaling the state). Well-designed L2s can also help, especially L2s optimized for specific applications (eg. high-volume trading, privacy...). These goals are even compatible with significantly lower slot times, thanks to Raul's work on erasure-coded P2P, and many other optimizations. The most high-value "product" of the ethereum blockchain, financially speaking, is ETH the asset. Ethereum secures $250 billion of ETH. The types of properties of Ethereum that I mentioned above are very good for ETH the asset. Nearly 90% of my net worth is in ETH, and most of the remainder is ~$40m of onchain fiat of which every dollar has already been allocated for some open-source biotech or software or hardware initiative. That said, there are aspects of supporting ETH the asset - *necessary* aspects even - that are outside the scope of the EF. This is where we need other heroes (some of whom hold more ETH than the EF does) to step in and help. EF has been recently thinking more about how it will relate to other such organizations, and give them needed initial support. EF will be a smaller ship than in previous years, a more opinionated one - in some cases more opinionated in ways that might be difficult to comprehend - but a longer-lasting one, and one suited to making sure that ethereum brings something meaningful to the world. We are grateful to all those inside and outside the EF who are helping to make this happen.