DFINITY Foundation

📣 Major Announcement! Applications are officially open for the #SDGBlockchainAccelerator. This edition is built for UN teams with an active programme, institutional backing and a concrete development challenge ready to move forward. The Accelerator will connect selected teams with expertise across #Blockchain and Decentralized #AI & #Cloud, supporting work in digital payments, digital identity, traceability and supply chains, data and privacy, and other emerging tech that can strengthen public systems and improve people’s lives. 🌟 Led by UNDP AltFinLab in strategic partnership with the Blockchain for Good Alliance (BGA), alongside the Cardano Foundation, Stellar Development Foundation, Partisia Blockchain, DFINITY Foundation and FLock.io. Apply by 30 September 2026: https://lnkd.in/dJPetxCW UNDP in Europe and Central Asia

ICP MCP. One agent. Every app. We asked Arshavir Ter-Gabrielyan, Team Lead for Identity at DFINITY, for the killer feature of the ICP MCP server. His answer: getting things done across your apps without switching between them. Think about moving your social account to a new platform by hand. Endless taps and swipes. Prompt an agent instead, and as long as it can sign in to both apps, it carries your posts, content, and connections across for you. The same holds for any job that spans more than one app. One chatbot, acting across all of them, wherever you are. That is where agents start to earn their place. Full interview linked in the comments.

Build and operate your ICP apps straight from your favorite AI. That is what the ICP MCP connector makes possible. In our interview, Arshavir Ter-Gabrielyan, Team Lead for Identity at DFINITY, walks through what it unlocks, starting with automation. Connect an agent to the apps you already use, then hand it the repetitive, multi-step work. Schedule it. Batch it. Let the agent work out how to connect the pieces into a bigger task, which is exactly what agents are good at. And there is nothing to wire up. Any app powered by Internet Identity gains these capabilities through a single connector, so one agent can act across all of them for you. Automation is just the first benefit. Insights, acting across your apps on the go, and fine-grained security controls all follow. The ICP MCP connector is in preview now, and you can try it yourself. Full interview linked in the comments.

Internet Identity is getting an MCP server. We sat down with Arshavir Ter-Gabrielyan, Team Lead for Identity at DFINITY, to talk through what it is, how it works, and what it makes possible. He starts with the problem. An AI agent runs in a cloud sandbox. It has no access to your device, so it has no safe way to hold your keys. That is what has kept agents from acting inside your apps for you. The MCP server changes that. Keys stay inside a trusted execution environment. The agent connects to the server, then requests permission to act in each app on your behalf. Full interview linked in the comments.

New look - same great NNS

Cloud Engines let any organization run its own sovereign compute at cloud scale, fully under its own control. In our interview, Björn Tackmann explains where SEV Subnets fit in. Choose SEV nodes to run your Cloud Engine on, and you can validate that all the data you store stays encrypted the entire time it's being processed. Confidentiality enforced by the hardware, not by a policy. For the workloads that need it, that's a real step up in what a Cloud Engine can offer. Full interview linked in the comments.

SEV Subnets on the Internet Computer come with a specific guarantee worth understanding: the node operators running the hardware cannot access the data being processed. In our interview, Björn Tackmann explains why this matters and how it works. The short version: SEV (Secure Encrypted Virtualization) encrypts memory at the hardware level. The encryption keys are managed inside the CPU and are never exposed to the host system. Even with full physical access to the machine, an operator cannot read what's running on a SEV Subnet. Most cloud security models rely on contractual commitments and audit trails. SEV Subnets make it a technical property of the infrastructure itself. For healthcare, finance, legal, and any workload where the "trust but verify" model isn't sufficient, that's a meaningful shift. Full interview linked in the comments.

SEV Subnets are now live on the Internet Computer. We sat down with Björn Tackmann, Senior Director of Engineering at DFINITY, to talk through what they are, how they work, and what they make possible. He opens with the foundational problem: when code runs on standard cloud infrastructure, data gets written to memory in plaintext. Anyone with access to the hardware can read it. This isn't a bug in any particular system. It's the default behavior of how computers have always been designed. SEV Subnets change that at the hardware level. Memory is encrypted. The node operators running the infrastructure cannot access what's being processed. And because this is built into the Internet Computer's subnet architecture, it scales. The rest of the conversation gets into what that enables for Cloud Engines and confidential compute at scale. Full interview linked in the comments.

Here's a short demo of email recovery for Internet Identity. The user registers an email from the manage page and confirms it by sending a one-off code. From a fresh device with no passkeys, the same email recovers access in seconds. A clean, mainstream-friendly path to never losing your identity. Set it up at id.ai

Login with Internet Identity is coming to the ICP CLI. From the command line you can get a delegation and use it locally, carrying your identity from one machine to another. The principal you use on the command line is the same one you use when logged in through Internet Identity, which makes it far easier to let an agent make calls on your behalf, with no extra identity or permissions to manage.