2026

Dario Amodei is one of the few frontier-lab CEOs whose public talking points have not changed materially in five years. The same message he gave to small audiences in 2021 - that powerful AI is coming faster than people think, that the safety problem is real, and that the companies building it have an obligation to do so carefully - is the message he is giving to Congress and Davos in 2026. The thing that has changed is that he now runs the company most aggressively turning that message into a commercial position. ...

TL;DR The blockchain industry in 2026 is no longer arguing about whether it has a future. The arguments are about which layers do which jobs. Bitcoin remains the reserve asset and the most credible neutral settlement layer. Ethereum is the dominant smart-contract base layer, with most activity now happening on its Layer 2s. Solana has taken the high-throughput application crown. Polkadot is mid-pivot from infrastructure to applications. The two structural shifts that define 2026 are modular blockchains (Celestia, EigenLayer) and the stablecoin economy, where annual settlement volume now exceeds Visa. Real-world asset tokenization has gone from a slide-deck thesis to a $30B+ live market, led by BlackRock’s BUIDL and tokenized US treasuries. The destination for the next two years is clear: payments, treasuries, and AI agents using crypto rails - and most users will not know they are using a blockchain. What Actually Survived It is worth saying out loud: most of the things that called themselves “the future of finance” in 2021 are gone. The 2022-2023 unwind cleared out the projects that had no users, no revenue, and no reason to exist. What remains in 2026 is a much smaller, much more boring, and much more useful set of networks. ...

TL;DR Low Earth orbit (LEO) in 2026 contains roughly 40,000 tracked objects larger than 10cm and an estimated 1 million pieces of debris between 1cm and 10cm. Most of it is dead satellites, spent stages, and fragments from past collisions or anti-satellite tests. The economics are a textbook tragedy of the commons. Each launch operator captures the upside of putting hardware in orbit. The cost of debris is shared across every other operator and every future mission. There is no global price on creating debris. The risk is non-linear. Kessler syndrome - a cascade where collisions create more debris that triggers more collisions - is not a hypothetical. We are already in the early stages in some altitude bands. The fix is also a textbook commons solution: price the externality. End-of-life deorbit requirements, debris remediation funds, transparent collision-avoidance markets, and active debris removal services. Some of this exists. Most of it is undersupplied. The realistic 2026 picture: not yet a crisis, on a trajectory that becomes one within a decade if nothing changes, with the most useful policy interventions being the ones that price debris creation directly rather than relying on goodwill. The Numbers Order-of-magnitude figures, drawn from ESA’s space debris office and LeoLabs tracking data, as of 2026: ...

TL;DR China’s space programme in 2026 is one of the most consistently executed national space efforts in history. Where Western programmes have lurched between budgets and political cycles, China’s CNSA has shipped roughly what it announced, on roughly the timelines it announced. The Tiangong space station is fully operational, continuously crewed, and has hosted both domestic and international experiments. The Chang’e lunar series has progressed from sample return (Chang’e 5, 6) to the precursors of a crewed lunar landing programme planned before 2030. China has now returned samples from both the near and far sides of the Moon - the only nation to have done so. The lunar plan centres on the International Lunar Research Station (ILRS) - a long-term, China-led, multinational lunar surface base, with crewed landings as a milestone rather than the goal. Mars sample return, deep-space exploration, and a permanent lunar presence are all on a credible timeline. The realistic 2030 picture is two distinct, durable lunar architectures - American and Chinese - running in parallel. Why It Is Worth Looking Carefully It is easy in Western coverage to treat China’s space programme as a backdrop to the Artemis story. That undersells what is actually happening. ...

TL;DR The self-hosted vs managed decision in 2026 is genuinely different from the same decision in 2022. The math has shifted in three directions: cloud egress costs, AI workload economics, and self-hosted tooling maturity. Managed remains the right default for most teams. The thing that has changed is that the threshold at which self-hosting becomes worth considering has dropped. Workloads that were obviously managed in 2022 are genuine 50/50 calls in 2026. The most important shift is that self-hosting is no longer synonymous with on-premises. Modern self-hosting often means renting bare-metal in a colocation, running your own clusters in a hyperscaler, or using sovereign cloud providers - all with different economics. For specific categories - AI inference at scale, data egress-heavy workloads, predictable steady-state compute, regulated environments - self-hosting now wins on cost more often than people assume. The honest framing: managed is the right default; self-hosting is the right minority case; the minority is bigger than it used to be. Why This Decision Got Harder For most of the 2010s the answer was easy. Managed services were cheaper than self-hosting once you priced in operational overhead. The cloud providers competed aggressively. Self-hosting was for the regulated, the eccentric, and the very large. ...

TL;DR eBPF is the technology that lets you run safe, sandboxed programs inside the Linux kernel without writing kernel modules. In 2026 it is the foundation under most serious observability, networking, and runtime security tools. The interesting story is not the technology itself - it is the wave of products built on top of it: Cilium for networking, Tetragon for runtime security, Pixie, Parca, and Coroot for observability, plus a long tail of vendor offerings using eBPF under the hood. For platform engineers, eBPF is not “a thing you have to learn to write.” It is a thing you have to know about so you can choose tools intelligently and understand what is happening on your nodes when those tools cause problems. The most important shift eBPF has enabled is observability without instrumentation. You can see what is happening on a system without modifying the application, without restarting it, and with low overhead. That is genuinely new. What eBPF Actually Is eBPF stands for “extended Berkeley Packet Filter,” which is historical and confusing because eBPF has long since outgrown packet filtering. The simple version: ...

TL;DR Data pipelines were optimised for human consumers - dashboards, BI tools, analysts. In 2026 a growing share of pipeline output flows directly to language models, agents, and retrieval systems. That changes the design constraints in ways that catch teams off guard. Aggregation matters less. Context fidelity matters more. Freshness behaves differently. Schema moves from rigid to negotiated. Cost shifts from compute to tokens. The biggest mistake is treating an LLM consumer as if it were just another dashboard. It is not. It does not skim, it does not interpret charts, it does not have working memory across rows. It needs to be fed. The new patterns - retrieval-aware partitioning, embedding pipelines, structured-document outputs, prompt-shaped views, evaluation harnesses for data quality - are the actual subject of “AI-native data engineering” in 2026. The Underlying Shift For thirty years the implicit consumer of every data pipeline was a human looking at a screen. Even when the pipeline ended in an API or a CSV, the conceptual end-user was someone who would interpret the output with judgement, context, and skim-reading. ...

TL;DR With the open table format wars largely settled, the strategic fight in 2026 has moved up to the catalog layer - the system that manages tables, namespaces, governance, and access. Four credible open or open-ish catalogs are now in serious play: Unity Catalog (Databricks), Polaris (Snowflake), Apache Gravitino (Datastrato/community), and Project Nessie (Dremio/community). All four implement the Iceberg REST catalog spec to varying degrees, which means clients can talk to them through a common protocol. The differentiation has moved to governance, multi-tenancy, lineage, federation, and developer experience. Unity is the most production-mature and the most coupled to Databricks. Polaris is the cleanest open implementation of the REST spec. Gravitino is the most ambitious in scope - aiming to catalog non-table assets too. Nessie is the most opinionated about Git-style branching for data. The winning catalog will probably not be a single project. It will be the protocol (Iceberg REST) plus multiple compliant implementations plus federation between them. That is the picture 2026 ends with. Why The Catalog Layer Matters Now A table format defines how data is laid out on disk. A catalog defines: ...

TL;DR The open table format war between Apache Iceberg, Delta Lake, and Apache Hudi is effectively over in 2026 - and the outcome is not a single winner but a clear settlement. Iceberg has won the role of the neutral standard that engines and platforms expect to read and write. It is the format you choose when you do not want to be coupled to a single vendor. Delta has won the role of the incumbent default inside the Databricks ecosystem and remains a strong choice if Databricks is your primary engine. Delta UniForm has narrowed the gap by letting Delta tables expose Iceberg metadata. Hudi has not won a category outright. It retains a smaller but loyal user base for streaming-heavy and CDC-heavy workloads, where its design choices still genuinely fit. The interesting battle has moved up the stack to the catalog layer. The format question is mostly settled. The catalog question is the new fight. The Format Wars - A Brief History For most of the early 2020s the lakehouse story was a three-way argument about how to put ACID transactions on top of object storage. ...

TL;DR “Onchain AI agents” became the dominant crypto narrative in 2025 and has cooled meaningfully in 2026 as the picture has gotten clearer. The honest taxonomy has three buckets: agents that hold wallets and trade, agents that automate DeFi operations, and agents that exist primarily as tokens with a chatbot attached. Only the first two are doing real work. Real revenue is concentrated in agent-driven DeFi automation, MEV strategies executed by agents, and onchain payment rails for AI services. Most of the rest is meme economics dressed in technical clothing. The structural question - “do AI agents need crypto rails at all” - has become a genuinely live debate. The answer in 2026 is “yes, but only for a narrow set of jobs, and most of those jobs are not what was being pitched.” If you are evaluating an onchain AI agent project, the test is brutally simple: strip away the token and ask whether the agent does something useful. If the answer is no, the project is a token with extra steps. How We Got Here The phrase “onchain AI agent” started showing up in crypto Twitter in late 2024 and exploded in early 2025. By the middle of last year there were thousands of agent tokens, dozens of agent platforms, and a handful of agents with billion-dollar implied market caps doing things that would have embarrassed a 2010-era chatbot. ...