RobTwo5

[dom | icp @dominic_w]

Hello MULTI/DEX 🔥 Should DFINITY release the most powerful DeFi application the world has ever seen?

What's cool about it? Here are some factoids, the craziest at the end:
1. It runs on an ICP cloud engine (soon everyone can have one) and is 100% network resident and tamperproof.
2. It is genuinely multi-chain, with no bridging hassles for users (users can deposit straight into their accounts, and withdraw directly, from the native chains of tokens).
3. It is order book based, but also provides a traditional swap interface, which swaps arbitrary assets by routing across the underlying markets.
4. It supports both spot trading, and margin trading that lets traders go long and short with leverage.
5. It has an AMM (Automated Market Maker) that uses Internet Computer outcalls to determine outside prices, then delayed matching against AMM limit orders to prevent arbitrageurs draining liquidity, as can occur with traditional DEXs providing swaps.
6. The AMM maintains a unified liquidity vault, and doesn't need two liquidity pools for every trading pair, providing outstanding capital efficiency and liquidity compared with traditional DeFi systems.
7. Users can earn by depositing into the AMM Vault, and into an insurance pool that protects the vault from margin calls that fail to recover all capital (the insurance pool gets 5% of all liquidations).
8. MULTI/DEX runs on the decentralized Internet Computer network, and is 100% open source — unlike HyperLedger, say, which remains closed source, and has an single-purpose architecture closer to federated CEX hosted on a symmetric cluster of federated servers.
9. If we go ahead, we would propose that MULTI/DEX runs as part of the Internet Computer, in the sense it is controlled and updated by the NNS (The Internet Computer's Network Nervous System, the world's largest and most sophisticated DAO, which directly orchestrates and updates the network) providing unparalleled levels of autonomy, transparency, and security.
10.... and this is the BIG ONE... its backend is built using the latest Motoko language framework (soon to be released) that puts AI *inside* of its software. That means, in another seminal inventive step from DFINITY and Caffeine Labs technology teams, that AI can see, browse and query the realtime data inside the app/dapp's persistent memory and can create and execute ad hoc queries and update logic on-the-fly (subject to permissions). So, while for much of the time traders will be using the traditional UX shown in the pic, increasingly, they will be interacting with the exchange through AI chats that have the "Internet Computer Connector" MCP installed (soon to be released). On the one hand, traders will be able to use chat to ask for simple things, like current spot pricing and market depth, and the likely slippage on a spot market order, and for orders to be submitted, but on the other, for much more demanding things that require the AI to execute ad hoc functionality, such as "Look at my positions and margin pools, and rebalance them to give me more blended market exposure, while also adjusting for risks indicated by social media coverage of forthcoming market events, but wait for my approval of your plan before proceeding."

This is a lot to take in, so I'm aiming to get a new demo video out ASAP that will demonstrate what's possible with this AIware, which will include MULTI/DEX — should be about a week!!

Btw. for those wondering what might be the big picture beyond what I just described with MULTI/DEX: At DFINITY, we are in the process of transforming ourselves into an "agentic organization," where all our existing apps/SaaS is replaced by custom on-demand apps/SaaS running on cloud engines that are created and updated by AI. Of course, these on-demand apps/SaaS are being built using the new technology described that automatically puts AI inside and provides users with fluid functionality via chat. The totality of the apps/SaaS represents an enterprise "World Model," which incorporates as much of the enterprise's data as possible, enabling AI to perform incredibly powerful analyses and actions — when you see this is in action, you can't unsee what you saw, because it's clearly a huge leap beyond the status quo of today's tech, which is exactly what the Internet Computer project is about. This wraps up our new technology stack, created by leaning on unique aspects of "The Network is The Cloud" paradigm, and years of work, and what, together with cloud engines, will finally enable the Internet Computer to strike out into the massive mainstream cloud technology market.

[dom | icp @dominic_w]

Soon I will demonstrate how AI can be "inside" an arbitrary ICP app, service or website built using the latest Motoko, understanding all its data, analysing it any way you want, and taking actions, without need for one special line of code. Insane and groundbreaking.

[DFINITY Foundation @dfinity]

Cloud engines run in three steps.

1) Select your nodes
Pick hardware, operators, geography. 4 to 100 nodes per engine, any continent.

2) Fund your engine
Pay in USD. Cycles power everything. No infra overhead.

3) Deploy your apps
Install from App Center or push direct. Connect your AI agent. Zero servers to manage.

One node fails. Apps keep running.

https://t.co/rrn4Ki3a7H

[dom | icp @dominic_w]

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 https://t.co/D5Dfj44BmO.

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 (https://t.co/ptsshOm9nj) 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 https://t.co/lloVYiGYs8 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 https://t.co/IfQrVovF3L 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!!

[dom | icp @dominic_w]

Internet Computer's 5th birthday on May 10th, 2026.

To celebrate, DFINITY will demo "cloud engines," including agentic builds, AI nodes, and more. This is a very big deal for ICP, cloud and agentic R&D. Engines will be the 1st frontier cloud/compute technology the wild⏱️

[dom | icp @dominic_w]

As https://t.co/1UYehNI8hQ transitions to V3, it is now clearer than ever.

There is only 1 onchain cloud network: the Internet Computer (ICP). There is no room for debate. After years of relentless R&D, the technology remains completely unmatched. And it's getting better 🔥.

[dom | icp @dominic_w]

Caffeine V3 is in dev, waiting for integration into main. It's an epic improvement. We're days away now 🔥

[DFINITY Foundation @dfinity]

DFINITY Foundation and the Government of Pakistan have signed an MoU to establish sovereign cloud infrastructure, generative AI app development, and secure national communications, on the Internet Computer.

The collaboration includes:
— Pakistan Subnet
— Caffeine AI Licenses
— National Messenger Service
— DFINITY in Pakistan

Through this decision, Pakistan furthers its digital sovereignty and AI push in line with announcements made by the prime minister at Indus AI Week.

1/4 🧵

[dom | icp @dominic_w]

The V2 Caffeine AI Engine ☕️ is live 👏. We've now shifted focus to shipping V3.

Claude Code unlocked AWESOME power for vibe coders, setting a new standard. V3 will unlock the same powers those building tamperproof apps using self-writing cloud on https://t.co/IfQrVovF3L | ICP.

You can expect V3 in weeks, not months, if things continue to go to plan!! I'm super excited because I believe the transition to V3 will mark a major inflection point in the history of Caffeine, by transforming what is possible for natural-language-only self-writing cloud builders creating apps onchain through retail, entrepreneurs and SMEs, to enterprise.

For this reason, we've decided to focus on V3 rather than continue to fettle V2. It must be shipped ASAP.

Meanwhile, Caffeine's monthly active users continues to grow rapidly, with hundreds of thousands of unique builders now using the platform every month, even though our marketing and growth effort is still very early.

I cannot say more now, but we are now readying a marketing, partnerships and PR push for the advent of V3. We are transforming..

As always, our ambition is to have *millions* of builders creating dapps on ICP before the end of 2026, and I continue to believe we will achieve that.

Regarding Web3, which we feel affinity to although ICP remains a round peg in a square hole, I'm proud to say, that we have now increased the number of builders across the ecosystem by an order of magnitude in just a few months (there are now more than 10X more builders on the Internet Computer than there are on all other networks combined).

This progress is truly incredible, and I applaud everyone working behind the scenes to make that possible. For now this achievement has only received very minor recognition within the Web3 industry, because of its continuing focus on tokenization, speculation, DeFi, and metrics that are often manufactured, like TVL and exchange volume.

But, it remains the case, that when people like me actually pioneered the "world computer" vision more than a decade ago now, in my own case by working on new applied cryptography and repurposing techniques from classical distributed computer science for the decentralized network setting, the aim was *always* to enable crypto networks to provide a revolutionary new kind cloud platform.

We saw that fully onchain tamperproof apps that ran safely without traditional cybersecurity protections, which were guaranteed to run, and many other things, including new forms of serverless software that combined logic and data, could be incredibly valuable across the board — and provide mainstream value that has nothing to do with tokens and speculation.

In fact, many early founders, and people like me, especially those associated with the early Ethereum project 2014-15, once saw tokenization as a use case for true world computers (essentially, onchain cloud), rather than the defining purpose of crypto networks.

Today, 90%+ of those building on ICP's onchain self-writing sovereign cloud come from mainstream backgrounds, and are primarily interested in *what* they can build, whether their apps will be tamperproof and sovereign, and AI agents updating their apps within guardrails that guarantee app data cannot be lost, and so on.

This is the first time that there has been mass market adoption of crypto network functionality that does not involve tokens and speculation. Caffeine will turn on Web3 functionality for builders soon, but currently they cannot access ICP's trustless multichain capabilities — for which reasons, obviously, the overwhelming majority are not building on ICP because it's a "new kind of blockchain."

For these reasons, ICP has now clearly delivered the first genuine mass market breakthrough for crypto networks since tokens and DeFi. But for people like me, this is simply going back to the future. It was this that brought us to crypto in the first place, not tokens and pure speculation.

We wanted to use decentralized networks and advanced computer science to deliver breakthrough utility that addressed seminal tech challenges including security and resilience, enabling autonomous software, sovereignty, and reducing the cost of creating and maintaining apps. In recent years, the intersection of this technology with AI has become a major area of work.

Soon, the ICP ecosystem's transition to the mainstream world will be further catalyzed by "cloud engines." Announcements are also approaching regarding other major advances and developments, particularly relating to sovereign cloud and AI.

Self-writing, and soon sovereign cloud, have provided ICP with a springboard into the $1 trillion revenue-a-year cloud market, and it will continue to grow from here.

We will to make "The Network is The Cloud" paradigm an important part of the cloud market, and we will begin change how the world understands crypto networks in the process.

2026 will be a huge year for ICP.

[dom | icp @dominic_w]

He's talking about ICP and Caffeine rescuing crypto here :)

Today, we have a proven world computer providing powerful sovereign onchain cloud. In the 3 months Caffeine has been available, 162k fully onchain apps were built, with 40k+ in production

Enabling dapps using ETH next

[Pierre @PierreSamaties]

To underline the significance of it:

Today: 70% of European cloud is US-controlled. Swiss companies want out.

Tomorrow: AI builds most software. It needs infrastructure it can't break.

The Swiss Subnet solves both.
→ Deploy apps in Switzerland, tamperproof and immune to cyber attacks
→ Give AI the safest stack to build, deploy, and run software

Launched today in Davos. 🇨🇭

More national subnets on the horizon!

[dom | icp @dominic_w]

Super excited, @SwissSubnet 1st national subnet launched @ WCD, Davos

Deploy apps on sovereign Internet Computer/ICP territory keeping all data and computation in Switzerland, to meet emerging regulatory and sovereignty objectives, and more

Next, Swiss Subnet cloud engines 💪🏼

[dom | icp @dominic_w]

Feb 2nd, https://t.co/c91gCXdahA will begin to roll out it's all-new fully agentic "automated tech team" (v2.0)

Big advances coming for self-writing cloud and ICP ☕💪

[OISY Wallet @oisy]

1/

OISY has upgraded its login to Internet Identity 2.0 - the new gold standard for privacy preserving digital identity.

This means a simpler and more familiar way to sign in with optional support for @Apple , @Google , and @Microsoft and no login number to remember.

[dom | icp @dominic_w]

An important new ICP white paper. This is a big one, enjoy! #Mission70

"Mission 70 and Accelerating the Internet Computer Economy"

https://t.co/T6HiI2wSUY

[DMAIL.AI @Dmailofficial]

Dmail DApp has launched the Storage Expansion Plan. Powered by @dfinity Canisters for secure, tamper-proof distributed storage.

Full data sovereignty: You own everything, forever.
No centralized servers – pure #Web3 privacy.
Scalable storage without limits.

Join thousands in the community and upgrade your email today! Explore Now: https://t.co/igbHNp8Wrr

#dmailers #Web3Email #ICP #Decentralized #privacy

[dom | icp @dominic_w]

2025 ICP realized onchain as cloud where AI builds too: performant, secure, resilient & no-data-loss guarantees

2026=Double Down
— mass market "cloud engines"
— better self-writing apps
— TRUE Web3 no-code
— builders ⬆️🚀

ICP boldly going where no network has gone before 💥

[DFINITY Foundation @dfinity]

The Internet Computer's storage capacity has grown dramatically.

At launch: ~50GB per subnet

Today: 2TB per subnet (40x increase)

With 47 subnets (94TB total replicated storage capacity), no other blockchain comes close to this amount of fully replicated storage.

Plus: Distributed storage coming soon for static assets that don't need smart contract access.

Both storage types. One platform.

[caffeine @caffeineai]

Caffeine Premium Subscriptions are ~ LIVE ~

In addition to monthly credits and top up options, say ‘Hello’ to:

>> custom domains
>> emails
>> analytics

Let’s take a closer look:

1/4

[DFINITY Foundation @dfinity]

The big day is finally here:

Congratulations to the winners of the Caffeine Demo Video contest 🎉

We have receive a vast number of submissions, but six creations truly stood out - It is our pleasure to officially announce the winners, who will be receiving 🏆 1,250 ICP each:

@The_PC_
@earlybird_icp
@FahimHaque77
@mindr3adr
@kelvindoa
@cheese_icp

A big thank you to everyone who participated. Your creativity blew us away. Therefore, we have prepared some special prizes for the 12 runner-up apps - check out the following posts in this thread and please keep your DMs open so we can deliver your rewards.
https://t.co/Bowu5tgcl8

1/3