The Internet Computer Protocol has rolled out two upgrades that expand how developers can interact with the wider internet from within its ecosystem. Canisters can now make HTTPS outcalls to both IPv6 and IPv4 addresses, removing a longstanding limitation and opening access to a broader range of services.
The process requires no changes to existing code. When a request is made, the system first attempts a direct IPv6 connection. If that fails because the destination is IPv4-only, it automatically retries via a SOCKS proxy managed by the network. The encrypted connection between node and destination remains intact throughout, with the proxy forwarding only the encrypted traffic, ensuring it cannot see or alter the content.
Alongside IPv4 support, the latest beta version of the Canister Development Kit introduces non-replicated outcalls. This means developers can instruct only a single, randomly chosen replica to perform an HTTP request instead of every replica on the subnet. It offers potential savings in both cost and redundancy when accessing non-idempotent endpoints, retrieving rapidly changing data, or making expensive API calls. However, the trade-off is that developers must trust the single replica’s response or verify it independently, as standard consensus checks are bypassed.
The feature is marked as experimental, with pricing and performance optimisations still in progress. Developers are being invited to test the new capabilities, give feedback, and help shape future enhancements. Plans under consideration include flexible replication options that could allow multiple responses from different replicas or even targeted calls to specific nodes, balancing cost, latency and trust in ways that fit individual project needs.
These upgrades point to a push for more versatile and developer-friendly outcalls on the Internet Computer, with the current release setting the stage for more granular control over how and where external data is fetched.
Dear Reader,
Ledger Life is an independent platform dedicated to covering the Internet Computer (ICP) ecosystem and beyond. We focus on real stories, builder updates, project launches, and the quiet innovations that often get missed.
We’re not backed by sponsors. We rely on readers like you.
If you find value in what we publish—whether it’s deep dives into dApps, explainers on decentralised tech, or just keeping track of what’s moving in Web3—please consider making a donation. It helps us cover costs, stay consistent, and remain truly independent.
Your support goes a long way.
🧠 ICP Principal: ins6i-d53ug-zxmgh-qvum3-r3pvl-ufcvu-bdyon-ovzdy-d26k3-lgq2v-3qe
🧾 ICP Address: f8deb966878f8b83204b251d5d799e0345ea72b8e62e8cf9da8d8830e1b3b05f
🪙 BTC Wallet: bc1pp5kuez9r2atdmrp4jmu6fxersny4uhnaxyrxau4dg7365je8sy2q9zff6p
Every contribution helps keep the lights on, the stories flowing, and the crypto clutter out.
Thank you for reading, sharing, and being part of this experiment in decentralised media.
—Team Ledger Life
Community Discussion