𝕀ℕ𝕊𝕀𝔾ℍ𝕋 @InsightICP

Tech, not tricks...

dom | icp @dominic_w

4 months ago

Only Internet Computer has real AI-relevance: 1) tamperproof platform agents build on e.g. caffeine.ai 2) since 2024 runs neural networks onchain as smart contracts, and 3) soon🤞 adding verifiable LLM inference at cloud-rivaling efficiency. Tech, not tricks...

68 195 768 43K 17

The business case for BigTech embracing cloud engines is off the charts One of the strongest business cases for anything in the history of business (will get into this tomorrow) **ALL IT WILL TAKE IS ONE OF THEM** $ICP $CLOUD ☁️♾️

Because ICP was never meant to be just another version of the Ethereum model (like 99% of "web3"). The goal was never simply token ledgers, micropayments, or ownership rails (although all of this is running better on ICP as well), but sovereign cloud infrastructure that uses blockchain and advanced cryptography to run apps and services in a tamperproof way - and provide the best infrastructure for agents to build and operate. That is a much bigger vision and one that can create real value for society.

🔴IMPORTANT ECOSYSTEM UPDATE DMAIL IS SHUTTING DOWN OPERATIONS (There are some big takeaways here about the future of tech-centric projects) Cloud Foundation is NOT shutting down operations $ICP $CLOUD ☁️♾ #MISSION100

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.

The first ICP cloud engines should definitely be in the Middle East!

Mario Nawfal @MarioNawfal

5 months ago

🚨🇮🇷 Iranian drones hit 3 Amazon AWS data centers in the Gulf. 2 in the UAE directly, 1 in Bahrain nearby. Iran's reason: the U.S. military runs AI intelligence systems on AWS. Including, they specifically claimed, Anthropic's Claude. The facilities are still partially offline.

keyboard_arrow_left Previous keyboard_arrow_right Next

85 590 2K 244K 152

I’ve been thinking more about vibe coding and host on the InternetComputerProtocol, and honestly I feel like the biggest thing holding it back right now is just the deployment experience. Right now, if you build something using the ICP skills and your own AI agent, it works, but the flow still feels a bit rough. You have to go through the CLI, use dfx, manage identities, top up cycles manually, and it’s not super intuitive if you’re coming from a typical vibe coding setup. What would make a huge difference is something simple: A clean ICP dashboard or NNS-style interface where you can: - log in with Internet Identity - drag and drop your app files (or paste your project) - see a live preview - hit deploy - done And for payments: - either use ICP you already have - or just link a credit card for auto top-ups So instead of thinking about cycles, wallets, and commands, it just works in the background like any modern hosting platform. Even better, CaffeineAI already feels like it’s halfway there. Imagine if you could: - either build inside Caffeine AI - or upload something you already vibe coded using the ICP skills - hit deploy - and it handles everything Then if you want to make changes, you don’t even have to edit files manually. You just tell the AI what to change and redeploy. That would basically turn it into: - AI builder - hosting platform - deployment tool all in one place. I feel like ICP already solves the hard problems: - full stack in one environment - built-in storage and auth - no need for multiple services Now it just needs that last step: a really smooth, no-friction deployment experience. If that gets solved, I think a lot more vibe coders would start using it without hesitation. $ICP $CLOUD @caffeineai @dfinity @dominic_w @PierreSamaties @bjoernassmann

@ICPsimp This is all correct, and it will be done

Caffeine V3 will remain full self-writing for now. But as a semi-technical dev, it's also incredible what you can create using Claude Code today by giving it the skill (which uses icp cli not dfx): skills.internetcomputer.org/llms.txt But the deployment process needs to be fixed asap. It's awful for sure. Caffeine may offer an alternative for use with vibe coding tools, but there needs to be general NNS0managed alternatives too along the lines that ICPsimp described.

Realizing ruggers got more support than my channel over the last 4yrs… $ICP $CLOUD ☁️♾️

Warren Buffet: "I can end the deficit in five minutes. You juts pass a law that says that anytime there is a deficit of more than 3% of GDP, all sitting members of Congress are ineligible for reelection."

🔴 IMPORTANT UPDATE KONG SWAP IS SUNSETTING THEIR PLATFORM THE ICP ECOSYSTEM HAS BEEN ANNIHILATED $ICP $CLOUD ☁️♾

ICP Was Just Used in a Real War — Here's What That Means. Simple explanation of what recently happened with #Canisterworm $ICP youtu.be/NNFTb9GacMs?si…

🔴ICP<>BIGTECH CLOUD | CLOUD FUSION CLOUD ENGINES ARE THE ENDGAME A Cloud Foundation Production ☁️📽️ $ICP $CLOUD ☁️♾

Someone finally found a use case for ICP 🤣 Definately Bullish 🚀🚀🚀

catpirate ∞ @catpirate33

5 months ago

"Trivy Supply Chain Attack Triggers Self-Spreading CanisterWorm Across 47 npm Packages" Hackers used $ICP ’s blockchain smart contracts as an almost indestructible command center in a large scale supply chain attack This appears to be the first publicly documented large-scale

11 19 79 10K 12

@VictorICP_ @lysergin33 Defo Bullish

"Trivy Supply Chain Attack Triggers Self-Spreading CanisterWorm Across 47 npm Packages" Hackers used $ICP ’s blockchain smart contracts as an almost indestructible command center in a large scale supply chain attack This appears to be the first publicly documented large-scale attack using $ICP, with attackers leveraging smart contracts as a decentralized command-and-control (C2) server. thehackernews.com/2026/03/trivy-…

Lmaoooooo I’m crying

AWS in Bahrain went down after drone hit. The ICP solution coming – apps and services hosted on ICP "cloud engines" running over multiple AWS data centers will be immune. tradingview.com/news/gurufocus…

The entire $ICP community now... #Mission70

keyboard_arrow_left Previous keyboard_arrow_right Next