$ICP $IC ❄️
This 2021 article from Dom is the original blueprint for the ETH + ICP convergence.
He laid out direct bidirectional calls: • Ethereum smart contracts → ICP canisters
• ICP canisters → Ethereum smart contracts
Enabled by Chain Key cryptography (threshold signatures). Canisters can control Ethereum addresses without ever holding a traditional private key.
That’s the foundation for ckETH, ckBTC, and the broader chain-key model.
The framing was always complementary, not competitive:
Ethereum = settlement + liquidity layer
ICP = high-capacity compute layer
That design is the architectural root of the icOS thesis:
1. Ethereum keeps deep capital, stablecoins, RWAs, and DeFi rails
2. ICP runs Cloud Engines, private subnets, long-running agent state, and AIware
3. Chain Key removes normal bridge risk so agents and Open SaaS can treat ETH liquidity as native while executing on sovereign ICP compute
4. The private root (zk$IC / shielded rails) is what makes it complete — transparent compute isn’t enough for institutions or high-value agents. Private subnets + zk turn the stack into a full privacy-preserving World Computer
The recent ckETH activity in the public docs is just the continued maturation of this exact path.
Hardware (chips) is the first wave.
The software substrate that turns those chips into a sovereign, private, agent-native execution layer is the second.
This is the long-duration claim.
medium.com/dfinity/internet-…