blue (@sundial369) header
blue (@sundial369) profile picture
Joined January 2023
Photo by blue (@sundial369)Photo by blue (@sundial369)Photo by blue (@sundial369)Photo by blue (@sundial369)Photo by blue (@sundial369)Photo by blue (@sundial369)Photo by blue (@sundial369)Photo by blue (@sundial369)Photo by blue (@sundial369)Photo by blue (@sundial369)
$ICP alone cannot scale the World Computer. $ETH itself cannot. $ZEC cannot. Zk wrapped USDC cannot. $IC ❄️
$ICP $IC❄️ $ETH The Balance in the Middle. ☀️
1
12
1,225
Give yourself a pat on the back You’ve suffered a lot
1
2
24
680
Edward Hopper
3
64
2
523
9,157
Vincent van Gogh - "Landscape Under a Stormy Sky" (1888)
2
225
5
1,441
18,338
blue retweeted
Now this is who should have been the main characters of GTA 6.
Lana Del Rey enjoys a night out in Miami with husband Jeremy Dufrene at GTA 6 launch event
78
1,151
22
23,904
333,541
The post is about the practical ability to deploy and update websites and apps on $ICP using Motoko, running them inside Cloud Engines. This is the infrastructure step that makes a later sovereign environment possible. A customer selects independent nodes. The protocol forms them into a subnet. The application is deployed as a canister. Its state lives inside the Engine. The Engine gives orthogonal persistence: the app’s memory survives node failures and continues without the customer managing servers or backups. Updates can be pushed safely because the Engine can reject a change that would destroy existing state. There is no separate server to log into and no vendor admin panel that can delete the app because a credit card expired. Persistent agents and Open SaaS tools will need a place where their state continues and where standing permission rules can be enforced without a single operator being able to rewrite the rules or read the memory. The Engine is that place. The customer chooses the geography and the node operators. The protocol guarantees the answer is the subnet’s answer. That is the foundation. The private rail $IC❄️🏴‍☠️ and the full operating surface are what come after. Fiat would enter as a normal subscription and convert to a shielded claim on Ethereum. The Engine would hold a chain-key twin. When a rule allows a draw, chain-key would produce the signature and the transfer would clear on Ethereum. The user would see a line on a bill. Crypto would stay in the background. The Engine would evaluate the rules and hold the persistent work.
It's time to ditch PHP. Here's how your website can move to Motoko, in under 20 seconds. Hand the job to your coding agent. Give it the migration skill, ask it to move your site, and it looks everything over and plans the move. Nothing changes until you say yes. Then it rebuilds the site in Motoko, the Internet Computer's programming language, and puts it live. Your pages and links stay the same, and there's no PHP runtime, web server or OS left to patch.
1
4
20
571
Dunder Mifflin
54
765
38
25,801
2,531,449
$ICP Ethereum is getting prepared for Cloud Engines. The case has become monetary for ETH, the programmable store of value people choose to hold and earn on, while fiat keeps losing purchasing power. That is the settlement side of the split. Ethereum is where the claim lives and where the final transfer clears. The agent’s memory, tools, and permission rules stay inside a Cloud Engine. When the rule allows a spend, chain-key produces the signature. The Engine evaluates. Ethereum records. The two stay separate. Fiat enters as a subscription. It converts to a shielded $IC❄️ claim on Ethereum. The Engine holds the twin and draws only when the rule permits. The user sees a line on a bill. Yield can still sit on the Ethereum side for collateral. The Engine does not have to host it. $ICP burns for the room. $IC is the claim the room is allowed to spend. This keeps Ethereum from absorbing every agent’s persistent state. State repricing and proof aggregation are already aimed at that problem. The Engine is the place the continuous work runs. The authorized $IC draw is what crosses. Lubin is describing the money. icOS is the room the money is allowed to leave. 🏴‍☠️
Soon organizations and individuals will realize that they are staring at two major financial life choices: (1) hold their money (as SoV ETH) and earn on top of that collateral money at solid yield (e.g. in the MetaMask Money Account at north of 5%) in an exponentially growing decentralized protocol economy, or (2) hold (depreciating fiat) money in low yield bank accounts or fiat-based instruments in an economy with high inflation making it hard to retain the purchasing power of that money. When citizens realize that they are being financially repressed by accelerating government money printing because their countries are very deep in debt, they will shout out their windows: "I'm mad as hell and I'm not going to take it anymore!" (e.g. Network 1976) Eventually the there will be an acceleration out of fiat money and into sounder and soon ultrasound money. en.wikipedia.org/wiki/Financ…
3
16
764
$ICP Ethereum is being positioned as the default settlement chain. Vitalik and the recent discussion around state repricing and proof aggregation keep pushing it toward a lean root of trust that can verify value transfers without absorbing every application’s persistent state. These Ethereum posts makes the other half explicit: the protocol’s guarantees do not automatically reach users through today’s frontends and RPCs. The application layer is somewhere else. Cloud Engines are one place it can live. The Engine is the room the customer chooses. The state lives there. The rules live there. When a rule allows a spend, chain-key produces the signature that settles on Ethereum. The user sees a subscription line. Crypto stays in the background. $IC❄️ is the private claim the Engine draws from. ICP burns for compute. The two networks stay complementary. Dominic wrote in 2021 that integrating Ethereum and the Internet Computer would rejoin the starting point of DFINITY, and that is exactly what they were going to do. @TailofIcy community has been mapping that split for the last year. The street is getting lighter. The house is still being built. The authorized draw is what clears when the rule allows it. 🏴‍☠️
Let's make an Ethereum where Cloudflare goes down and you don't lose access Let's make an Ethereum where a hacked website can't trick you into signing your money away Let's make an Ethereum where no single company can shut you out Let’s make an Ethereum where you never have to trust a middleman to use it
1
2
1
14
771
Chase, Bank of America, Wells Fargo, and several other American national banks are reporting major nationwide outages this afternoon across the United States.
4
6
62
1,006
$IC❄️ is the gem everyone in crypto was always looking for. The default layer of the ai economy. The culmination of blockchain. $ICP
3
5
1
20
1,014
Icy
ICYMI: ⚡️ Vitalik Buterin says EIP-8037 is the most practical way to scale Ethereum while preserving decentralization, arguing unrestricted state growth would violate “Ethereum’s fundamental guarantees.”
1
4
191
Ernest Lawson Windy Day, Bronx River
3
42
575
$ICP Caspar, the account Vitalik has been reposting, just called ETH the “root of trust for the world.” That is the street in the icOS stack. That is the functionality and language to be used for ETH, Tail of Icy lead us to seeing. Ethereum is where deep liquidity and stablecoins already live. It is the place a shielded claim can sit and where an authorized draw can settle. Caspar’s argument is that Ethereum stays valuable by remaining neutral, secure, and architecturally capable of being that root — not by chasing maximum fees or becoming the place every agent runs. The house is the Cloud Engine. That is where the agent lives, the rules are enforced, and the work actually runs. Chain key lets the Engine control an Ethereum address without a key on any single machine. When the rule allows the spend, the claim moves. When it does not, nothing happens. $IC is the private balance that sits on the root of trust and gets drawn by the Engine. It is not the fuel. $ICP is burned for compute. $IC is the claim the operating system holds so the kitchen never has to name a wallet. The street stays the root of trust. The house stays sovereign. The claim stays in the wall. $IC ❄️
4
10
813
EXCLUSIVE: Dominic Williams on Cloud Engines, AI Agents & ICP’s Next Chapter We didn’t let AOL own the internet. Why did we let three companies own the cloud? In this interview, I sit down with DFINITY founder Dominic Williams (@dominic_w) to discuss Cloud Engines and his bet that AI agents will change how software is built, and which infrastructure wins. After 46 years of writing code, his verdict on his own role is striking: “I’m a super expert software engineer. I’m obsolete.” We get into sovereign cloud infrastructure, OpenSaaS, Pakistan’s early work with ICP, and the proposed model connecting Cloud Engine payments to ICP burning. As Cloud Engines enter early access, this is the thinking behind the rollout. Watch the full 42-minute conversation. @dfinity Recorded in Dubai ahead of the rollout. Chapter timestamps below.
40
196
18
611
136,325
$ICP is about to a solve a real world bottleneck. And the current tech push will open up another bottleneck further down stream, already being worked on to guarantee default layer functionality and use. Cloud Engines and Open SaaS fix problems that already exist. They give you a building you own instead of an apartment you rent. You pick the location, the locks work the way you want, and no landlord can change them or throw your stuff out. Open SaaS is the first furniture you can bring into that building with ordinary effort. That is real progress. It is also still infrastructure plus applications. Once people put real work and capable agents inside those buildings, different problems show up. One is shared context with different rules. Several agents work from the same memory. One is allowed to spend on certain things. Another can look but not spend. A third can write but not send. These distinctions are normal. Right now almost every tool has its own idea of who is allowed to do what. When a new tool is added, or someone comes back after a few weeks, the rules have to be set up again. The information stays. The rules do not travel with it. That coordination work grows with the number of agents and becomes the bottleneck. Another is the interface. Once agents are good enough, people stop wanting to open individual apps. They just say what they want: prepare the summary and send it, but do not renew any outside subscriptions. If the only option is a list of installed tools plus a chat window, the user is still managing the doors. The Engine made the building trustworthy. It did not remove the job of remembering which door leads where and who is allowed in which room. The third is continuity. An agent that has to be started from scratch every time, or that has to be watched because it might spend on the wrong thing, or that loses the context when the session ends, does not reduce the work. It adds another thing someone still has to manage. These problems appear after the rooms and the furniture exist. More nodes or cheaper cycles do not solve them. They are solved by a layer above the individual tools: a place where rules can be set once, tools appear when needed and disappear when finished, and ordinary money moves in the background. That layer turns the durable building into the environment people actually use. The Engine remains necessary. The operating surface is what removes the remaining administrative work once the agents are capable enough that the old application model becomes the constraint. ethereum:0xa876f27f13a9eb6e621202cefdd5afc4a90e6457❄️
I guess that leaves only the Internet Computer in the "world computer" game then, building on hardcore technical work since 2014 ;) Cloud engines this week ✌🏼..
2
7
30
860
Microsoft is sharting on the bathroom floor… and ethereum:0xa876f27f13a9eb6e621202cefdd5afc4a90e6457 ❄️ IS 1m mc… $ICP
2
15
627
blue retweeted
Look deeper. $IC ❄️🏴‍☠️
Look deeper.
1
4
17
609