JonnyWQ.icp

Into the Future | ∞ 8 year gang ∞ #ICP

[dom | icp @dominic_w]

Nearly every solopreneur, startup, SME, enterprise or government department, will want to become an agentic organization (or "cybernetic org").

They will be vastly smarter, faster and more efficient.

Internet Computer Protocol (ICP) helps enable this brave future. But how? 🧵

[dom | icp @dominic_w]

The https://t.co/0HZSEGHqwo portal is designed to be autonomous and run as an integral part of the Internet Computer network. It will thus be updated by the NNS, the network's inbuilt decentralized governance system = sovereign frontier cloud from an open network.

[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]

Someone got Wordpress running 100% from the Internet Computer! Not as easy as it sounds, as it's designed to run on traditional tech, not frontier serverless cloud, so big shout out to ICP community member @miadey 🔥

https://t.co/OB6LYKbIaO

[dom | icp @dominic_w]

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:

[dom | icp @dominic_w]

#Mission70 progress:

Gen-1 node rewards now reduced by 40%, and NNS voting rewards by 36.7%.

Total ICP inflation reduced by 33.4% ✅

Deflationary pressure: cloud engines on track, self-writing cloud use is growing ✅

Much more to come :)

[JonnyWQ.icp @JonnyWq]

@NVIDIAGeForceDE PRAGMATA RTX

[dom | icp @dominic_w]

@its_daxxx I think we'll see Starlink used as a backup to national fibre links between data centers hosting ICP cloud engine nodes (data centers, and terrestrial and sub-sea internet cables, have become targets of war, sabotage and terrorism).

[JonnyWQ.icp @JonnyWq]

@Zero2HeroZombie Who burned it? Where can I find that?

[Jabotinsky Jew @CrazyVideosOnly]

I wasn’t expecting that response😭

[DFINITY Foundation @dfinity]

What is Internet Identity 2.0?

👤 Internet Identity 2.0 is the authentication service on #ICP enabling real privacy, with quick, safe and hassle-free sign-in.

Check it out: 👉 https://t.co/TavUu6G3YW

[Mike ∞ @BigBossPassion]

Cycle burn rate on $ICP had 10x growth year after year. Last year it was over 100x growth. Just imagine one more year of 10x growth. Game over for bears. Btw CBR is currently at 600B even without BOB. 🔥

[dom | icp @dominic_w]

Internet Computer is soaking up relentless and eye-popping growth rn 💪

Remember the World Computer vision from 2014? #ICP is currently doing 1.5 million ETH-equivalent TX/s, measured as VM instructions executed.

[dom | icp @dominic_w]

Internet Computer #ICP deck update
– High-level explanations
– Easter Eggs 🥚⚡️

🌐 https://t.co/QGlx6XUjWF

[Kyle @kylelangham]

It's Sept 9, not even 9 full days into September, and it's already been a crazy huge month for the Internet Computer Protocol. Here's 5 things that happened...

[Ajki @ajki76]

#InternetComputer $ICP community is abuzz with excitement over a playful project, https://t.co/8JHQuznmox (blockchain on blockchain), where $ICP computing resources are utilized to mine the $BOB token, leading to a unique fair launch.

Although this isn't a serious usage of $ICP's capabilities and is comparable to meme coins, it has a notable impact due to $ICP's design, which includes a burn mechanism that makes it deflationary.

One of the benefits of such entertaining projects is their ability to attract new users, some of whom may explore other dApps within the $ICP ecosystem, creating a mutually beneficial scenario.

Imagine if @bobdotfun evolved into a fair launch platform where anyone could create their own token ticker... It's almost overwhelming to consider, as $ICP would rapidly burn through its supply.

Before getting overexcited about the entire supply being burned, it's crucial to understand that #InternetComputer is a general computing blockchain.

It doesn't use $ICP for computation; instead, it uses cycles, which are pegged to the SDR (basket of five major currencies, with 1 SDR equal ~$1.3).

By burning $ICP, you can acquire 1 trillion cycles per SDR. This design ensures that the cost of hosting is not tied to the $ICP price. Consequently, as the price of $ICP rises, less $ICP is needed to obtain the same number of cycles, meaning less $ICP will be burned.

[Crypto ₦ł₦ℑ₳ ∞ @Crypt0_Ninja_]

⚠️Exclusive Insight: #Allianz #Bank Developing New Product on #ICP Network

I have inside information that #AllianzBank is currently developing a groundbreaking product that will tokenize assets on the #Internet #Computer (#ICP) network. As part of this initiative, they are training programmers in the #Motoko programming language.

This could be a major step forward in the integration of blockchain technology with traditional financial products. 🚀

[dom | icp @dominic_w]

Blockchain x AI 🧠 and #ICP @dfinity

What's here, what's coming and what I think – fresh off the press, a fireside with Tracy Trachsler!

[ICP Japan @icphub_JP]

【♾️ICP × Ethereumで、より多くのユーザーがDeFiプロトコルにアクセス♾️】
この動画では、Liquity バージョン2というEthereumをベースとした新しい分散型金融（DeFi）プロトコルと、そのプロトコルにおけるInternet Computer (IC)の重要な役割について説明しています。
https://t.co/fVQhTWXEIU

ICPのキャニスター（スマートコントラクト）上に構築された #自動金利管理モジュール が、システムの効率性と信頼性を大幅に向上させます。#Ethereum の広範なエコシステムとセキュリティ、#ICP の高速処理と低コストを組み合わせることで、より強力で効率的な #DeFiプロトコル を構築できます。

✅Liquity バージョン2の概要:
■ 2024年11月にリリース予定の新し��DeFiプロトコル（具体的な日付は未確定）
■ 借り手が独自の金利を設定・調整可能（現行Liquityからの主要な改善点）
■ 新しいステーブルコイン（仮称：「Bold B」）を発行
■ 金利に基づく借り手のリスト管理
■ 償還メカニズムによるステーブルコインの安定性維持償還メカニズム：ステーブルコイン保有者が1コインを1ドル相当のETHと交換可能
→→→これにより、コインの価値が1ドルから大きく乖離することを防止

✅ICPの重要な役割:
a. #自動金利管理モジュール:
■ ICPのキャニスター（スマートコントラクト）上に構築
■ ユーザーの金利管理を自動化・効率化
■ ICPの「リバースガス」モデルによるガス代の削減 - ユーザーの取引手数料をゼロにすることが可能
b. #戦略的金利管理:
■ リスキー、中程度、保守的な3つの戦略を提��
■ 「ターゲットデットインフロント」に基づく管理 - 借り手リスト内での目標位置を設定し、市場状況に応じて調整
■ 市場状況に応じた動的な調整
c. #自己持続可能なシステム:
■ 管理手数料の導入
■ キャニスターの維持とガス代の支払いを自動化

✅ICPの重要性:
a. #スケーラビリティ:
■ 多数の借り手の金利を効率的に管理
■ バッチ処理によるガス代の削減
b. #信頼性と自動化:
■ 人的エラーのリスクを軽減
■ 24/7稼働の自動管理システム
c. #カスタマイズ性:
■ ユーザーのリスク選好に応じた戦略選択
■ 市場状況に応じた動的な調整
d. #インターオペラビリティ:
■ EthereumベースのLiquityとICPの統合
■ クロスチェーン機能の実現

✅ICPとEthereumの統合理由:
■ Ethereumの既存エコシステムと流動性の活用
■ ICPの高スケーラビリティと低コストの利点
■ L2ソリューションと比較して:より高い処理能力と柔軟性
より広範な相互運用性の可能性
■ リスク分散と段階的な技��採用

この統合により、Liquity バージョン2は現行のDeFiの課題に対処しつつ、次世代のDeFiプロトコルの基準を設定することを目指しているようです。ICPの活用は、単なる技術的改善を超えて、DeFiプロトコルの効率性、信頼性、アクセシビリティ、そして将来性を大きく向上させる重要な戦略的決定と言えます。

[dom | icp @dominic_w]

Crazy prediction: black hats will become the biggest marketeers of tamperproof #ICP compute platforms by driving a global cybersecurity meltdown that hasn't even gotten started yet...