Hanna π¨π¦π±π§ retweeted
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.
Hanna π¨π¦π±π§ retweeted
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 opencloud.org.
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 (internetcomputer.org) 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 skills.internetcomputer.org 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 caffeine.ai 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!!
Hanna π¨π¦π±π§ retweeted
WooCommerce is now running on WordPress inside WASP on ICP
This is a huge milestone.
uiukd-xyaaa-aaaad-qhonq-cai.β¦
We are not just running a static site.
We are not just running a basic WordPress page.
We are now running real plugin-heavy PHP workload inside ICP canisters.
No VPS.
No traditional hoster.
PHP + WordPress + WASQL + WooCommerce on ICP.
Load times are improving progressively, and we are getting closer to something big:
A decentralized hosting layer for the existing PHP and WordPress world.
WASP is building the bridge from Web2 to Web3.
Hanna π¨π¦π±π§ retweeted
People asking what ICP "cloud engines" β the Internet Computer as frontier onchain cloud for agents building apps, services and systems - actually looks like.
Here's approximately what's coming:
Hanna π¨π¦π±π§ retweeted
Caffeine v3.0 βοΈ, Tuesday, April 7th
caffeine.ai
A new era begins on ICP in a few days. A huge Caffeine upgrade will take place. This is about more than the new features it packs: what can be built on the Internet Computer through chat alone shall advance by a quantum leap.
It will blow your mind, because you can go so much further: those wanting to build apps and services on self-writing cloud, where every technical task is automated and directed by natural language interaction, may rationally decide that the Internet Computer is the place to be thanks to the work of Caffeine Labs.
But, stunning as the v3.0 advance is, this only marks the beginning of a new beginning for ICP. Caffeine is just getting started, and will be joined by other major advances unfolding in the ICP ecosystem. Several things are coming together:
1) The architecture that powers Caffeine v3.0 will ensure it continues to grow more powerful as time goes on. We expect that it will be possible for non-technical people to build almost anything on the Internet Computer in the future. Eventually special features like "Caffeine Snorkel" will also make it possible to auto-migrate legacy apps and services to the Internet Computer.
2) For the first time, Caffeine will allow all users to publish the App Market, so that other users can install copies of their apps, and if they want, remix them, since apps from the market are mutable and can be changed as needed. This is important change will be followed by the activation of monetization features, which will kickstart a new open source onchain economy based around the AI-driven development of re-usable apps and services.
3) Caffeine apps use ICP Blob Storage (which is currently exclusively available to Caffeine owing to its ongoing development) to maintain copies of files and binary large objects. Coming advances will enable Caffeine apps to store data at the world's best $/GB β making the Caffeine the perfect plartform to use to build apps that must store and share large amounts of data (for example, for a photo sharing app, or a team communications platform where video meetings are routinely recorded and archived).
4) Caffeine will soon be joined by new ICP "cloud engine" functionality, and then, the Internet Intelligence Network (IIN) βΒ two new parts of the Internet Computer. Cloud engines will provide enterprise users with much more control over how the Internet Computer hosts their apps and services. IIN will provide everyone with access to inference on open weights models at lower cost than is possible today (for example allowing a business to create an e-commerce website on the Internet Computer where every customer can be helped through product exploration by AI, without worrying about the cost).
5) Cloud engines, which are essentially private subnets that can be controlled via a control panel, enable the Internet Computer to provide a cloud experience that feels more familiar to prosumers and enterprises used to centralized clouds. Users will be able to select the nodes combined to power their cloud engines, and nodes can include cloud-on-cloud nodes, such as AWS instances, as well as traditional sovereign node hardware. These nodes can be chosen to match precise throughput needs, or regulatory requirements (e.g. GDPR). The Internet Computer is thus transforming into a mass market cloud solution.
6) Powerful additional advantages of cloud engines include a) since they are essentally Internet Computer subnets, as usual hosted apps and services are tamperproof and unstoppable, and don't require support by security and systems administration personnel, b) hosted apps can have their query throughput auto-scaled horizontally by adding nodes, which can be located in proximity to demand, and can have ther update throughput auto-scaled by splitting the engines β enabling auto-scaling where software does not have to be updated βΒ and c) owners can traverse underlying compute vendors and geographies and jurisdictions, simply by adding and deleting nodes, which can be done without interrupting hosted apps.
7) The Internet Intelligence Network is an extension to the Internet Computer that we plan to propose to the NNS soon (which I have mentioned before). This will be powered by community-operated hardware devices, which crucially, in combination with new technology we are developing, shall shall facilitate provision of lower per-token inference costs than AI clouds can currently achieve within targeted market segments (low costs that are derived from the technology involved, in contrast to certain contemporary decentralized GPU networks that use token appreciation to drive unsustainable subsidization flywheels).
8) A key unique additional aspect of IIN is that inference is verifiable, just like onchain compute β that is, those supplying prompts and context will know that their results are correct, and shall not have to trust that the IIN nodes powering inference haven't changed their results (for example, by inserting advertising, or malicious content). The strength of the verification is configurable. In the default mode, there will be no discernible difference in cost or performance/time thanks to the techniques developed. In higher security modes, useful for special high-security purposes, verification cost will scale linearly with every node checking the inference, while the hit to performance/time remains very small. (Note that because inference is non-deterministic, inference verification is technically challenging and novel, and will advance the state-of-the-art).
In all, v3.0 is part of the Internet Computer's march towards the mainstream cloud market, which is predicted to generate $1 trillion in revenue in 2026, and $2 trillion in 2030.
While we see the Internet Computer as a revolutionary decentralized cloud platform, rather than a network beloning to the web3 industry per se, we note that after tokens (Bitcoin), and DeFi (Ethereum), onchain cloud is the first new decentralized network functionality to unlock mass market potential β and it's happeing exclusively on the Internet Computer, which is by far the most technologically advanced network the world has ever seen.
ICP is advancing to define an important new cloud sector, where the network is the cloud, and the cloud is self-writing.
Hanna π¨π¦π±π§ retweeted
My $BTC Dominance Indicator is live on $ICP
I was able to build this application in 1 hour using @caffeineai βοΈ
I hope you enjoy itβ¬οΈ
btcindicator-1b9.caffeine.xyβ¦
PS: This is just a test to display the capabilities of βοΈ It is not my final product. I will build something even better in the near future. Stay tuned!
Hanna π¨π¦π±π§ retweeted
β‘ Major privacy advance β‘
β
Apps run e2e on public network
β
User data is 100% encrypted
β
Multi-user/secure data sharing
β
No backdoors
medium.com/dfinity/onchain-pβ¦
Hanna π¨π¦π±π§ retweeted
Watch the full Caffeine demo by @dominic_w
Apply for early access: join.caffeine.ai
Hanna π¨π¦π±π§ retweeted
$ICP fam !!!
the new dashboard is badass !!!
dashboard.internetcomputer.oβ¦
Replying to @SunwingVacay
@SunwingVacay strikes again! The return flight is as horrible as the arrival one. From 4pm pushed to 3am, lack of communication on every front, no one answers the phone or the chat, no idea on accommodations, bus arrival, everyone at the gate with no clue when weβre actually leaving. Supposed to be gone by now but here we are 3am in Punta Cana and apparently they canβt find the pilot. How is this okay as a business!?
Replying to @SunwingVacay
@SunwingVacay you have a terrible airline business. Terrible service, delays with no communication, none of the staff seem to have a clue. From 9am to 4am and weβre still stranded, delay after delay in 3h intervals with bullshit excuses. Never again
Crew arrived to the wrong gate. You canβt make this stuff up. The level of confusion is concerning.
1
36
Hanna π¨π¦π±π§ retweeted
Bybit is handling the hack admirably, best wishes from DFINITY.
Re: hackers "musking" the Safe UX, this shouldn't even be possible, but traditional smart contracts can't securely serve UX from chain.
In 2018, I had DFINITY develop smart contracts for ICP that can serve UX themselves, directly from chain.
This was 1) to prevent "musking" happening to dapps on the Internet Computer, and 2) also to provide a means for other chains to obtain similar security (more below).
I have been talking about this specific web3 security problem for a long time. In fact, as part of the early Ethereum community, in 2015, I discussed this problem with Martin Koppleman himself, the founder of Gnosis, the source of Safe.
I have long believed in genuinely fully-onchain web3, where web applications, and other services, are constructed from advanced smart contracts that serve their web experiences from the blockchain themselves, directly to users.
The Internet Computer introduced this at launch, May 2021, but this capability remains unique in the industry: thus, while the Safe service holds tokens inside smart contracts on Ethereum, which define the multisig access control logic, the Safe web experience was actually served from somewhere else.
To be clear: the Safe UX/user experience (i.e. the web experience users interact with) does not benefit from end-to-end blockchain security.
The hackers knew its web experience was not being served from the blockchain, and found a way to modify it, musking the UX for the user, and making it display misleading information and tricking multiple signers.
Although multiple signers had to sign, they were all tricked into signing the same bad transaction, because the musked UX they were interacting with told them they were signing something else!
One of the following probably happened: 1) the web assets (html, js, etc) were modified at source, wherever that was, or 2) a network node proxying the web content on its way to the signers' web browsers, was able to maliciously modify the content (a third possibility is that they all had malware on their computers, but that seems less likely).
When smart contracts are serving the web experience themselves, then problem (1) cannot happen, and if there is a concern that problem (2) is a risk, and security concerns are high, then this can also be prevented with certainty.
(Technical tip: if you need to be sure (2) is impossible when interacting with ICP dapps, simply install this software, which checks the "chain key" signatures on all assets served from the Internet Computer github.com/dfinity/http-proxβ¦.)
The good news for the World Computer (which I define as the amalgamation of all blockchains that can host tokens and smart contracts), is that the Internet Computer can fix this for *everyone*.
The Internet Computer's "chain key" engine enables its smart contracts to sign smart contract transactions that run on *other* blockchains (currently Bitcoin, Ethereum and Solana also have native API-level support on the network, and this is expanding).
This means that it's possible to build web experiences on the Internet Computer that trustlessly build on smart contracts hosted by other blockchains. In this case, Safe's UX could have been built on the Internet Computer, while the exact same smart contracts on Ethereum could have been used.
It's time for crypto to end these endless hacks by creating web3 experiences that are hosted on the blockchain end-to-end (this is what the Internet Computer community means by "fully onchain").
The good news is we have been working on these problems for years, and the technological solutions are here, and already highly mature.
For those new to this fully onchain paradigm, here are some useful links that help illustrate the different world that is possible:
oisy.com β a 100% onchain multi-chain wallet, which you authenticate to using Internet Identity passkey technology, whose underlying smart contract software, which maintains your tokens, and serves you the web experience you interact with, is updated by the ICP's Network Nervous System (one of the largest and most secure DAOs in the world today)
oc.app β a 100% onchain chat service and social network, where you can send "chain key" bitcoin in chat messages at almost zero cost, with 1 second finality. This is also fully autonomous, and its smart contract software is updated by its own DAO.
github.com/dfinity/http-proxβ¦ β this is an open source project developing an app designed to run on the Internet Computer, which can be used to create a decentralized versions of Fireblocks (i.e. to maintain custody of multichain assets, and define complex workflows). Institutions seeking more security and decentralization in their crypto asset custody processes, can contact DFINITY for help using the software.
Let's keep working across our industry, in a non-partisan way, to bring these security problems to an end, once and for all πͺ
Some thoughts on the recent hack(s).
There is a pattern where hackers were able to steal large amounts of crypto from multi-sig βcold storageβ solutions, as with ByBit, Phemex, WazirX and potentially others. In the most recent ByBit case, the hackers were able to make the front-end user interface show a legitimate transaction while the actual signing was for a different transaction. I am less familiar with the other cases, but they sound similar based on limited available info.
Whatβs more scary is that the affected exchanges used different multi-sig solution providers. The hackers, the Lazarus Group, are highly advanced and broad in their abilities to penetrate. It is still unclear whether the hackers were able to penetrate multiple signing devices, or the server side, or both in each of these cases.
Some people questioned my suggestion of halting all withdrawals as a standard security precaution (in a tweet I posted from a shuttle bus to the plane). My intention was to share a practical approach based on my experiences and observations, yet there is no absolute right or wrong in either approach. My guiding principle is always to lean on the safer side. After any security incident, pause everything, make sure we fully understand what happened, how hackers penetrated the systems, which devices were compromised, triple-check all is safe, and then resume operations.
Pausing withdrawals could cause more panic, of course. In 2019, we paused withdrawals for a week after a massive $40 million hack. When we resumed withdrawals (and deposits), we saw more deposits than withdrawals. Not saying this is a better approach. Every situation is different. Itβs a judgment call. My tweet was to share what might work and my intention was to show support in a timely manner. I am sure Ben made the best decision based on the info he had.
Ben did a good job maintaining transparent communication and calmness in dealing with a challenging situation. That shows a sharp contrast to other less transparent CEOs, like WazirX, FTX, etc.
The cases mentioned here are all different. FTX was fraud. WazirX, I will refrain from commenting as there is an ongoing lawsuit.
Most importantly, we should never take security for granted. It is important to learn about security yourself so that you can choose the right tools for your needs. For this, I will share an article I wrote a few years ago. Itβs a little outdated, but the fundamental concepts still apply. Stay SAFU! binance.com/en/blog/from-ourβ¦
Hanna π¨π¦π±π§ retweeted
Buy Canadian
Support Canadian
Letβs also follow Canadian π¨π¦
Like β€οΈ & RT π this tweet
Reply with your favourite Canadian X account, letβs help grow Canadians on social media.
The future of ICP
By popular demand, here's a detailed post about caffeine.ai and the forthcoming "self-writing internet" (SWI) paradigm we in the ICP community are working to realize ππ§
If you prefer pics, checkout my deck at deck.icp.ai. Otherwise here goes...
Caffeine is meant for everybody. Using natural language, anybody will be able to create sovereign websites, web apps and internet services.
It might be an individual wanting to create something like a personal branding website, wedding planning app for their family, or portal for a sailing club. It might be an entrepreneur lauching an e-commerce website, or a sharing economy app with advanced Web3 rails. It might be a company or gov. dept. that needs a corporate portal, or some specific CRM (Customer Relationship Managment), ERP (Enterprise Resource Processing) or ARP (Accounts Receivable Processing) functionality.
The SWI paradigm is broad, and it involves anyone and everyone being able to create and own anything online from scratch, just by talking to AI. Over time, as the paradigm becomes more and more powerful, this will increasingly empower, democratize and decentralize tech worldwide.
Today, Large Language Models (a type of AI) have already become very good at writing code, and their abilities are continuing to improve rapidly. The Caffeine platform leverages this ability in combination with new specialized SWI infrastructure and technology that is being deployed to the Internet Computer network. This new tech infra has been especially designed to empower and enable AI to build effectively and safely solo on receipt of natural language instructions, without receiving any technical assistance from humans.
Caffeine has also been carefully designed to allow technical people, such as engineers and user experience designers, to build alongside AI, with purposes such as accelerating time-to-market, dramatically reducing costs while increasing quality, and using the AI as a tutor to learn new skills.
It's important to know that AI building apps solo is only one part of the SWI paradigm. It also involves apps and services being created on the decentralized internet, rather than inside some company's proprietary centralized platform, and drawing on this difference to provide 4 very important, defining characteristics:
1. Sovereignty
The SWI paradigm produces apps and services that become accessible via URLs (the addresses we enter into web browsers) that are *sovereign.* This property results from them being entirely hosted (running) on a decentralized, public network, in exactly the same way a bitcoin token lives on the Bitcoin blockchain. They are constructed from secure network-resident code/next-generation smart contracts, without any centralization or traditional backend IT needing to be involved, such as cloud computing services. This means that apps are not dependent on intermediaries that might censor them, or which might inflict harmful actions like massively hiking prices, which services typically seek to make them captive customers by locking them into their platforms. In addition, the underlying software and data of apps created by SWI belongs exclusively to their owners (which might be humans, an organization, DAO or yet another kind of entity), further preventing intermediaries gaining leverage. In production, these sovereign apps are controlled by a wallet (or assigned to a DAO, say), rather than a cloud account operated by a company.
2. Tamperproof security
Those building using traditional IT often euphemistically say their web apps and services are "secure," because they have carefully configured their cloud accounts to prevent exploits, and have purchased cybersecurity measures to protect hosted platform software like databases and their traditional custom code. However, in reality, such traditional IT infrastructure can never be truly secure, since the cybersecurity protections involved are highly fallible. In complete contrast, the websites, web apps and internet services created on SWI are "tamperproof," which means they are fundamentally secure, and don't need traditional cybersecurity measures for extra protection. This makes it much easier for AI to build solo, and also frees app owners from having to trust that centralized traditional IT service providers and SaaS platforms will successfully keep their data and systems secure using cybersecurity systems, which they cannot guarantee even if they wish to, because traditional IT is fundamentally insecure, and can only be patched by cybersecurity measures.
3. Updatable in production
The SWI paradigm requires that the owners of the apps and services produced can update them almost in real-time, simply by issuing additional natural language instructions to an AI, essentially evolving them at chat speed (in practice, with owners issuing instructions, and then refreshing the URL where their app is located). If you are non-technical, I need to tell you that this requirement is far more challenging than it might sound. Firstly, the process of upgrading/updating apps running in production must be sufficiently swift to occur at chat speed, which requires that the data involved can be transformed into new formats quickly. Secondly β and this is the really tough one β it is required that when the AI modifies the underlying software logic, and performs any required transformations/migrations of the app's data, that no data is accidentally lost, for example because the AI has made a mistake, which LLMs will continue to do because of the way they work, even as their overall abilities continue to improve.
4. Trustless Web3
SWI apps can incorporate many different types of functionalities, including AI functionalities. But there is a form of functionality that cannot be safely implemented on traditional IT stacks: Web3 functionality. SWI apps can securely hold and process tokens on multiple blockchains, trustlessly and seamlessly incorporating them into their own functionality, without requiring users use cumbersome traditional crypto wallets, which undermine user experience, and are themselves are vulnerable to hacks. The Internet Computer, in combination with the traditional blockchains it is directly interoperable with, forms a World Computer. The Internet Computer already hosts many onchain services that process tokens from multiple traditional chains, without the involvement of bridges and other systems that are often centralized in practice (note that in Web3, oftentimes people refer to apps built in a centralized way using traditional IT, which run on servers and compute platforms like Amazon Web Services, as "onchain," simply because they have an associated token, but in reality of course they are not, and therefore, cannot provide these guarantees). A great example of what's possible with the fully network-resident paradigm is , OpenChat, an open internet service that runs on the Internet Computer, which enables its users to instantly send bitcoins, ETH and SOL inside chat messages (the Internet Computer's "chain key" technology enables it to play the role of a kind of Layer 2 for blockchain assets). SWI will be able to build apps and services with similar functionality. Where required, those apps can also maintain their own treasuries using stablecoins (e.g. tokenized dollars) and other crypto innovations.
DFINITY is performing a wide range of technical work related to SWI. For example, we have an AI team that works with LLMs to make them better at coding SWI apps using specialized training and RAG infrastructures, and we are working to make efficient, seamless ICP network scaling even better, in anticipation of increased demands on the network created by SWI, and many other things, but in this post I'll talk more about our Motoko work.
Technical note (skip don't balk!): The Internet Computer hosts an entire serverless cloud, in which canister smart contracts are hosted and run, within a "virtual execution environment," which leverages the WebAssembly/Wasm virtual machine. (The virtual execution environment is hosted with the network's stateful decentralized network protocol, which is called Internet Computer Protocol, or ICP, which the network's sovereign node machines process).
This means both human developers, and AI, can write code in any programming language that compiles to Wasm byte code. Several languages are now popular in the ecosystem.
However, back in 2018, 3 years before the network launched, DFINITY decided to develop a completely new programming language for ICP platforms, called Motoko. Aside from applying advanced emerging concepts in programming language design, we were pursuing a number of objectives with Motoko:
1) To create a new, broadly accessible, simple-to-learn language, that was nonetheless powerful enough to build complex systems (addressing shortcomings of simple languages like JavaScript).
2) To create a language that leveraged special aspects of the Wasm virtual machine standard.
3) To create a language that was specifically designed for the Internet Computer's virtual execution environment, and some of the incredible advancements in the field of compute that it provides (in technical speak, Motoko is DSL/domain specific language).
Motoko is far more sophisticated and powerful than something like Solidity or Move, and developing a new language from scratch is not a simple undertaking, but we set to the task.
We were no doubt helped by the team being initially led by Andreas Rossberg, a co-inventor of WebAssembly, and leader within the Wasm community, who joined the DFINITY team in early 2017. He helped form a brilliant languages team, which continues to carry the torch today.
At some point, we realized that when AI builds solo, it might benefit from a language like Motoko, and thus, critical aspects of the language's design are being developed to empower human and AI developers alike.
Prima facie, without any special training, LLMs coding using Motoko already make far less mistakes than using Rust, an increasingly popular modern systems-programming language β despite their being far more training material available for Rust, in the form of online documentation, and open source code repositories.
But by developing special materials for training LLMs, and new technologies for Motoko, we are taking this much further.
One of the key advancements provided by ICP, is that software runs within a compute environment that providing something called "orthogonal persistence" (but don't balk, this is easy, keep reading!!)
This essentially means that software logic runs within persistent memory pages, and it's no longer necessary for developers to use database servers and file systems to persist data. In a sense, logic and data have become one, because developers can just define logical abstractions, and the data then automatically persists within them.
In summary, orthogonal persistence:
1) Massively simplifies software design, making it more abstract, which greatly helps AI.
2) Improves performance, since application data no longer has to be copied in and out of databases and files (this is part of the magic that allows, say, a social network to be built on the Internet Computer, while there is still not a single traditional blockchain that cfan store a simple photo taken with a phone).
Motoko development is leaning into orthogonal persistence, and I expect within 10 days, will release "enhanced orthogonal persistence," or "EOP," which takes things further still, especially with respect to AI empowerment.
With EOP, when canister smart contracts written in Motoko are upgraded, where the structure of data does not need to be transformed, it can be left completely alone during upgrades. This is another simplification, which will greatly help human and AI developers alike. But there's more...
When the SWI paradigm creates complex web applications and services online, inevitably changes to the structure of data in memory may occur.
For example, image an e-commerce website, with a Product object. The owner of the site might decide they wish to add comments functionality to listed products, which would require a Comments field being added to Product. At this stage, during the upgrade, the old Products objects must be transformed into new Products objects, and with EOP, some migration logic must thus be created.
EOP ensures that transformations can occur quickly, which is crucial for allowing SWI apps and services to be upgraded at chat speed, but it also addresses an even more important need.
Due to their design, LLMs will always occasionally hallucinate, and even though they are smart, they will make mistakes (and considering they are coding hundreds of times faster than humans, this is no surprise). What then if an AI building solo makes a mistake in the migration logic, causing app or service data to be lost?
For example, what if the AI defined the new Product format, adding the required comments feature, but in the process caused previously entered product data to be lost? (Of course, Caffeine will provide snapshotting and restore functionality, but this is last resort, not something a non-technical developer simply talking to build will want to use.)
The answer is that in EOP, when an upgrade is installed, the Motoko language platform checks the migration logic against the currently installed version to check that no data will be lost β and simply fails if it would be, forcing the AI to try again.
This is called "loss safe" programming, and it was invented at DFINITY.
I understand this is a bit of a technical story, but hopefully you can see that the "updatable" requirement of SWI is challenging to implement in practice, and thus that EOP delivers another groundbreaking ICP advance that will help AI and human builders alike.
None of this comes easy. Many aspects of EOP were envisaged back in the early days, but it has taken many years to realize the technology.
What is clear, is that AI must be empowered to build solo, because that is the future: AI is not human, and in the SWI paradigm, AI is required to build and update apps and services extremely rapidly, at the speed of chat.
To make all this possible, the bottom line is that AI requires its own environment to build in.
ICP already provides a tamperproof compute environment, so that a mistake by AI cannot lead to a hack and data exfiltration, or the installation of ransomware say β it is truly secure.
ICP already provides an unstoppable compute environment, relieving AI of the need to create things like failover and backup and restore systems, massively further simplifying software logic, enabling the AI to focus on what, not how, and further reducing the risk a mistake might cause data to be lost.
Now, Motoko's EOP will further accelerates upgrades on ICP, allowing them to run at chat speed, and most importantly, creates guardrails that prevent a simple mistake by AI causing data to be lost.
Of course, this is not all, and over time, I will have more to share with you about our SWI work.
What I hope I have conveyed, is that SWI is a new and emerging technical field, which is one that the Internet Computer, and the ICP community, is uniquely positioned to capitalize upon
In the future, human developers will build alongside AI developers (to reduce friction, we are also developing an in-browser development environment, called icp.ninja).
But also in the future, all 8 billion humans on earth without technical skills will also gain the ability to develop and own tamperproof and unstoppable sovereign websites, web apps and internet services, just by speaking in their local natural language.
When we release Caffeine, that will be only a beginning of a long and incredible journey into the future.
The SWI paradigm has no limits. As AI gets smarter, and as Caffeine, and the underlying SWI technology and infrastructure on the Internet Computer improves, it will be possible to create increasingly advanced apps and services.
Individuals, entrepreneurs, businesses, and governments, will increasingly choose to leverage SWI to create sovereign custom apps and services that are completely under their control, that they can update, customize and improve just by talking at any time of their choosing, and which slash their time to market and costs by orders of magnitude compared to today's tech β and the total addressable market will become unimaginably vast.
We want the SWI to explode on the Internet Computer, and are working towards that goal.
More news soon πͺ
51
Hanna π¨π¦π±π§ retweeted
After the leak of the @caffeineai demo video there have been a lot of questions and excitement. Iβm not part of the Caffeine team, but let me try to answer some of themβ¦
Does Caffeine give you access to the code?
Absolutely. You can see in the demo by Dom that Caffeine shows you the Motoko code in realtime (there is a βcodeβ button). You also become the controller of the canister created and have access to the github repo if you want to.
Canβt other apps do what Caffeine does?
The agent-to-code market is massive and thereβs a lot of competitors. Caffeine does a few things that give it a 10x advantage in this market, including writing both frontend and backend code, creating frictionless deployment of full applications (key word is frictionless β every point of friction loses users), is permissionless and, most importantly, can manage the entire software application and its data lifecycle without loss of user data. NOTE - all of these advantages make Caffeine extremely competitive in the massive web2 space. The fact that every app launched is web3-ready is only the cherry on the top.
Wen launch?
Only a few people know, and Iβm not one of them. Pls stop asking me :)
What about a token?
Another topic I donβt know anything about other than the public tweets.
Seriously, what makes Caffeine+ICP special?
I canβt stress this enoughβ¦ ICP is an ideal platform for significantly reducing the friction of full stack deployment. It has a significant advantage over web2 stacks, which inherit significant complexity in trying to join code and data. As agent-to-code applications drive the complexity of creating code down, and as the market demands deployment options for those applications, ICP offers a massive competitive advantage due to its combination of code and data in a single environment.
Whatβs in it for ICP holders?
Anyone will be able to launch ICP apps without coding experience AND will be able to manage their app lifecycles through Caffeine. Millions of applications on ICP equals cycle burn and millions of new users onboarded. But, more importantly, this is a chance for ICP to compete not just in the smaller web3 market, but to actually achieve a competitive advantage over web2 competitors.



















