☭ Comrades! Krasnograd '93 opens its gates. Rob kiosks, smuggle vodka, pick your neighbour's pocket and climb from Gopnik to Pakhan, in a living 3D Soviet town, fully on-chain on #ICP. Closed beta: reply or DM for an invite code. citxg-6iaaa-aaaai-aya2q-cai.…

How Do I Connect My IC Backend to Web2 APIs? Your Internet Computer $ICP backend can call Web2 services using HTTPS outcalls. Your canister sends a secure request, the network performs the HTTPS call, and the response comes back on-chain. 🧠 How it works Your canister calls the system method http_request. The Internet Computer performs the HTTPS request and returns the response. It works just like a normal backend, but fully decentralized. ⚙️ Consensus vs. Non-Consensus Calls There are two modes of HTTPS outcalls on the IC: Consensus calls • All nodes perform the request • The network agrees on the same response • Fully trustless, fully decentralized • Ideal for public APIs and deterministic data Non-consensus calls • Only one node performs the request • Faster and cheaper • Good when full decentralization isn’t required • Useful for real-time data or less predictable APIs 💡 Most developers use consensus calls for reliability and integrity, and non-consensus calls when performance or flexibility is more important. 🧹 Transform function Some Web2 APIs include unstable headers like timestamps. A small transform step cleans the response so nodes can agree on one result. 💸 Who pays? The canister pays in cycles, so users never need tokens or gas. ✨ You can fetch Web2 data, call external APIs, or trigger workflows. Directly from your on-chain backend, no oracle needed.

How do URLs work on the Internet Computer? On the Internet Computer, websites and apps don’t live on corporate servers but directly on the network itself. So, how do you reach them? Every app or website on the IC runs inside a canister: a smart container that gets its own unique URL. When you visit that URL, your browser connects through a boundary node, which securely routes your request to the right canister running on the network. Example: A website hosted on the Internet Computer can be reached at: l5wk7-miaaa-aaaal-acfla-cai.… Or, even better, you can link your own custom domain like: rem.codes/, while it still runs fully on the Internet Computer. Your URL becomes a direct gateway to decentralized apps on the open internet. $ICP

It’s like a microservice on the blockchain. It handles your logic, stores your data, and can even serve your frontend. You can build, among other things: 🌐 Websites 🔗 APIs 📊 Dashboards ⚙️ Connected services Basically, anything you’d host in a Web2 stack, but on a system that’s open, verifiable, and runs without any middleman. That’s the power of canisters on the Internet Computer. $ICP

The Internet Computer is an open platform where developers can run complete applications, not just smart contracts, directly on the network. Frontends, backends, and storage all live on-chain, providing a secure, decentralized alternative to traditional cloud hosting. 💡 Build social apps, tools, or games 🔗 Integrate with other blockchains 🌍 Host directly from the internet itself It’s the next step for open, trustless infrastructure where software truly runs on the web, not just on someone else’s server. $ICP

The rem.codes Developer Series is coming ! It will be fully dedicated to hands-on tutorials for building on the Internet Computer Protocol (ICP). Exciting things are on the way 👇 🎥 youtube.com/@rem_codes_ic 📸 instagram.com/rem_codes