dfinity · marc0olo · Feb 27, 2026
@@ -0,0 +1,2 @@
+Cargo.lock
+frontend/src/bindings/
@@ -1,113 +1,26 @@
 # Continue building locally
 
-Projects deployed through ICP Ninja are temporary; they will only be live for 20 minutes before they are removed. The command-line tool `dfx` can be used to continue building your ICP Ninja project locally and deploy it to the mainnet.
+Projects deployed through ICP Ninja are temporary; they will only be live for 30 minutes before they are removed. To continue building locally, follow these steps.
 
-To migrate your ICP Ninja project off of the web browser and develop it locally, follow these steps.
+### 1. Install developer tools
 
-### 1. Install developer tools.
-
-You can install the developer tools natively or use Dev Containers.
-
-#### Option 1: Natively install developer tools
-
-> Installing `dfx` natively is currently only supported on macOS and Linux systems. On Windows, it is recommended to use the Dev Containers option.
-
-1. Install `dfx` with the following command:
-
-```
-
-sh -ci "$(curl -fsSL https://internetcomputer.org/install.sh)"
-
-```
-
-> On Apple Silicon (e.g., Apple M1 chip), make sure you have Rosetta installed (`softwareupdate --install-rosetta`).
-
-2. [Install NodeJS](https://nodejs.org/en/download/package-manager).
-
-3. For Rust projects, you will also need to:
-
-- Install [Rust](https://doc.rust-lang.org/cargo/getting-started/installation.html#install-rust-and-cargo): `curl https://sh.rustup.rs -sSf | sh`
-
-- Install [candid-extractor](https://crates.io/crates/candid-extractor): `cargo install candid-extractor`
-
-4. For Motoko projects, you will also need to:
-
-- Install the Motoko package manager [Mops](https://docs.mops.one/quick-start#2-install-mops-cli): `npm i -g ic-mops`
-
-Lastly, navigate into your project's directory that you downloaded from ICP Ninja.
-
-#### Option 2: Dev Containers
-
-Continue building your projects locally by installing the [Dev Container extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) for VS Code and [Docker](https://docs.docker.com/engine/install/).
-
-Make sure Docker is running, then navigate into your project's directory that you downloaded from ICP Ninja and start the Dev Container by selecting `Dev-Containers: Reopen in Container` in VS Code's command palette (F1 or Ctrl/Cmd+Shift+P).
-
-> Note that local development ports (e.g. the ports used by `dfx` or `vite`) are forwarded from the Dev Container to your local machine. In the VS code terminal, use Ctrl/Cmd+Click on the displayed local URLs to open them in your browser. To view the current port mappings, click the "Ports" tab in the VS Code terminal window.
-
-### 2. Start the local development environment.
-
-```
-dfx start --background
-```
-
-### 3. Create a local developer identity.
-
-To manage your project's canisters, it is recommended that you create a local [developer identity](https://internetcomputer.org/docs/building-apps/getting-started/identities) rather than use the `dfx` default identity that is not stored securely.
-
-To create a new identity, run the commands:
-
-```
-
-dfx identity new IDENTITY_NAME
-
-dfx identity use IDENTITY_NAME
-
-```
-
-Replace `IDENTITY_NAME` with your preferred identity name. The first command `dfx start --background` starts the local `dfx` processes, then `dfx identity new` will create a new identity and return your identity's seed phase. Be sure to save this in a safe, secure location.
-
-The third command `dfx identity use` will tell `dfx` to use your new identity as the active identity. Any canister smart contracts created after running `dfx identity use` will be owned and controlled by the active identity.
-
-Your identity will have a principal ID associated with it. Principal IDs are used to identify different entities on ICP, such as users and canisters.
-
-[Learn more about ICP developer identities](https://internetcomputer.org/docs/building-apps/getting-started/identities).
-
-### 4. Deploy the project locally.
-
-Deploy your project to your local developer environment with:
-
-```
-npm install
-dfx deploy
+Install [Node.js](https://nodejs.org/en/download/) and [icp-cli](https://cli.icp.build):
 
+```bash
+npm install -g @icp-sdk/icp-cli @icp-sdk/ic-wasm
 ```
 
-Your project will be hosted on your local machine. The local canister URLs for your project will be shown in the terminal window as output of the `dfx deploy` command. You can open these URLs in your web browser to view the local instance of your project.
-
-### 5. Obtain cycles.
-
-To deploy your project to the mainnet for long-term public accessibility, first you will need [cycles](https://internetcomputer.org/docs/building-apps/getting-started/tokens-and-cycles). Cycles are used to pay for the resources your project uses on the mainnet, such as storage and compute.
-
-> This cost model is known as ICP's [reverse gas model](https://internetcomputer.org/docs/building-apps/essentials/gas-cost), where developers pay for their project's gas fees rather than users pay for their own gas fees. This model provides an enhanced end user experience since they do not need to hold tokens or sign transactions when using a dapp deployed on ICP.
-
-> Learn how much a project may cost by using the [pricing calculator](https://internetcomputer.org/docs/building-apps/essentials/cost-estimations-and-examples).
+Then navigate into your project's directory that you downloaded from ICP Ninja.
 
-Cycles can be obtained through [converting ICP tokens into cycles using `dfx`](https://internetcomputer.org/docs/building-apps/developer-tools/dfx/dfx-cycles#dfx-cycles-convert).
+### 2. Deploy locally
 
-### 6. Deploy to the mainnet.
-
-Once you have cycles, run the command:
-
-```
-
-dfx deploy --network ic
+Start the local network and deploy the project:
 
+```bash
+icp network start -d
+icp deploy
 ```
 
-After your project has been deployed to the mainnet, it will continuously require cycles to pay for the resources it uses. You will need to [top up](https://internetcomputer.org/docs/building-apps/canister-management/topping-up) your project's canisters or set up automatic cycles management through a service such as [CycleOps](https://cycleops.dev/).
-
-> If your project's canisters run out of cycles, they will be removed from the network.
-
 ## Additional examples
 
 Additional code examples and sample applications can be found in the [DFINITY examples repo](https://github.com/dfinity/examples).
@@ -1,28 +1,67 @@
 # EVM Block Explorer
 
+[View this sample's code on GitHub](https://github.com/dfinity/examples/tree/master/rust/evm_block_explorer)
+
+## Overview
+
 The EVM Block Explorer example demonstrates how an ICP smart contract can obtain information directly from other blockchain networks. Using HTTPS outcalls, smart contracts on ICP can interact with other networks without needing to go through a third-party service such as a bridge or an oracle. Supported interactions with other chains include querying network data, signing transactions, and submitting transactions directly to other networks.
 In this example, you'll also see how to sign transactions with canister ECDSA or Schnorr signatures.
 
 ## Deploying from ICP Ninja
 
-When viewing this project in ICP Ninja, you can deploy it directly to the mainnet for free by clicking "Run" in the upper right corner. Open this project in ICP Ninja:
+This example can be deployed directly from [ICP Ninja](https://icp.ninja), a browser-based IDE for ICP. To continue developing locally after deploying from ICP Ninja, see [BUILD.md](BUILD.md).
+
+[![Open in ICP Ninja](https://icp.ninja/assets/open.svg)](https://icp.ninja/i?g=https://github.com/dfinity/examples/rust/evm_block_explorer)
 
-[![](https://icp.ninja/assets/open.svg)](https://icp.ninja/i?g=https://github.com/dfinity/examples/rust/evm_block_explorer)
+> **Note:** ICP Ninja currently uses `dfx` under the hood, which is why this example includes a `dfx.json` configuration file. `dfx` is the legacy CLI, being superseded by [icp-cli](https://cli.icp.build), which is what developers should use for local development.
 
-## Build and deploy from the command-line
+## Build and deploy from the command line
 
-### 1. [Download and install the IC SDK.](https://internetcomputer.org/docs/building-apps/getting-started/install)
+### Prerequisites
 
-### 2. Download your project from ICP Ninja using the 'Download files' button on the upper left corner, or [clone the GitHub examples repository.](https://github.com/dfinity/examples/)
+- [x] Install [Node.js](https://nodejs.org/en/download/)
+- [x] Install [icp-cli](https://cli.icp.build): `npm install -g @icp-sdk/icp-cli @icp-sdk/ic-wasm`
 
-### 3. Navigate into the project's directory.
+### Install
 
-### 4. Deploy the project to your local environment:
+Clone the example project:
 
+```bash
+git clone https://github.com/dfinity/examples
+cd examples/rust/evm_block_explorer
 ```
-dfx start --background --clean && dfx deploy
+
+### Deployment
+
+Start the local network:
+
+```bash
+icp network start -d
+```
+
+Deploy the canisters:
+
+```bash
+icp deploy
+```
+
+Stop the local network when done:
+
+```bash
+icp network stop
+```
+
+## Updating the Candid interface
+
+The `backend/backend.did` file defines the backend canister's public interface. The frontend TypeScript bindings are auto-generated from this file during the frontend build.
+
+If you modify the backend's public API, rebuild the canister and regenerate the `.did` file:
+
+```bash
+icp build backend
+candid-extractor target/wasm32-unknown-unknown/release/backend.wasm > backend/backend.did
 ```
 
 ## Security considerations and best practices
 
-If you base your application on this example, it is recommended that you familiarize yourself with and adhere to the [security best practices](https://internetcomputer.org/docs/building-apps/security/overview) for developing on ICP. This example may not implement all the best practices.
+If you base your application on this example, it is recommended that you familiarize yourself with and adhere to the [security best practices](https://docs.internetcomputer.org/building-apps/security/overview) for developing on ICP. This example may not implement all the best practices.
@@ -10,8 +10,9 @@ crate-type = ["cdylib"]
 path = "lib.rs"
 
 [dependencies]
-candid = "0.10.13"
-evm-rpc-canister-types = "4.0.1"
+candid = "0.10.23"
+evm-rpc-canister-types = "5.0.1"
 hex = "0.4.3"
-ic-cdk = "0.17.1"
+ic-cdk = "0.17.2"
+ic0 = "1.0.1"
 sha2 = "0.10.8"
@@ -0,0 +1,30 @@
+type Block = record {
+  miner : text;
+  totalDifficulty : opt nat;
+  receiptsRoot : text;
+  stateRoot : text;
+  hash : text;
+  difficulty : opt nat;
+  size : nat;
+  uncles : vec text;
+  baseFeePerGas : opt nat;
+  extraData : text;
+  transactionsRoot : opt text;
+  sha3Uncles : text;
+  nonce : nat;
+  number : nat;
+  timestamp : nat;
+  transactions : vec text;
+  gasLimit : nat;
+  logsBloom : text;
+  parentHash : text;
+  gasUsed : nat;
+  mixHash : text;
+};
+service : {
+  get_ecdsa_public_key : () -> (text);
+  get_evm_block : (nat) -> (Block);
+  get_schnorr_public_key : () -> (text);
+  sign_message_with_ecdsa : (text) -> (text);
+  sign_message_with_schnorr : (text) -> (text);
+}
@@ -1,7 +1,7 @@
-use candid::Nat;
+use candid::{Nat, Principal};
 use evm_rpc_canister_types::{
-    Block, EthMainnetService, GetBlockByNumberResult, MultiGetBlockByNumberResult, RpcServices,
-    EVM_RPC,
+    Block, EthMainnetService, EvmRpcCanister, GetBlockByNumberResult,
+    MultiGetBlockByNumberResult, RpcServices, CANISTER_ID,
 };
 use ic_cdk::api::management_canister::{
     ecdsa::{
@@ -14,7 +14,22 @@ use ic_cdk::api::management_canister::{
     },
 };
 
-const KEY_NAME: &str = "test_key_1"; // Use "key_1" for production and "dfx_test_key" locally
+const KEY_NAME: &str = "test_key_1"; // Use "key_1" for production
+
+/// Resolve the EVM RPC canister ID at runtime. icp-cli sets the
+/// `PUBLIC_CANISTER_ID:evm_rpc` env var; fall back to the well-known mainnet ID.
+fn evm_rpc() -> EvmRpcCanister {
+    let name = "PUBLIC_CANISTER_ID:evm_rpc";
+    let id = if ic0::env_var_name_exists(name) != 0 {
+        let mut buf = vec![0u8; ic0::env_var_value_size(name)];
+        ic0::env_var_value_copy(name, &mut buf, 0);
+        let val = String::from_utf8(buf).expect("env var is not valid UTF-8");
+        Principal::from_text(&val).expect("Invalid evm_rpc canister ID")
+    } else {
+        CANISTER_ID
+    };
+    EvmRpcCanister(id)
+}
 
 #[ic_cdk::update]
 async fn get_evm_block(height: u128) -> Block {
@@ -43,7 +58,7 @@ async fn get_evm_block(height: u128) -> Block {
 
     // Call `eth_get_block_by_number` RPC method (unused cycles will be refunded)
     let cycles = 10_000_000_000;
-    let (result,) = EVM_RPC
+    let (result,) = evm_rpc()
         .eth_get_block_by_number(
             rpc_providers,
             None,

@@ -3,27 +3,24 @@
   "private": true,
   "type": "module",
   "scripts": {
-    "prebuild": "npm i --include=dev && dfx generate backend",
+    "prebuild": "npm i --include=dev",
     "build": "vite build",
     "dev": "vite"
   },
   "dependencies": {
-    "@dfinity/agent": "2.4.1",
-    "@dfinity/auth-client": "2.4.1",
-    "@dfinity/candid": "2.4.1",
-    "@dfinity/principal": "2.4.1",
-    "react-json-view-lite": "2.3.0",
+    "@icp-sdk/core": "~5.0.0",
     "react": "18.3.1",
-    "react-dom": "18.3.1"
+    "react-dom": "18.3.1",
+    "react-json-view-lite": "2.3.0"
   },
   "devDependencies": {
+    "@icp-sdk/bindgen": "~0.2.2",
     "@types/react": "18.3.12",
     "@types/react-dom": "18.3.1",
     "@vitejs/plugin-react": "4.3.3",
     "autoprefixer": "^10.4.20",
     "postcss": "8.4.48",
     "tailwindcss": "3.4.14",
-    "vite": "5.4.11",
-    "vite-plugin-environment": "1.1.3"
+    "vite": "5.4.11"
   }
 }
@@ -1,5 +1,5 @@
 import React, { useState } from 'react';
-import { backend } from 'declarations/backend';
+import { backend } from './actor';
 import { JsonView, allExpanded, defaultStyles } from 'react-json-view-lite';
 import 'react-json-view-lite/dist/index.css';
 

@@ -1,5 +1,5 @@
 import React, { useState } from 'react';
-import { backend } from 'declarations/backend';
+import { backend } from './actor';
 
 function Block() {
   const [loading, setLoading] = useState(false);

@@ -1,5 +1,5 @@
 import React, { useState } from 'react';
-import { backend } from 'declarations/backend';
+import { backend } from './actor';
 
 function Block() {
   const [loading, setLoading] = useState(false);

@@ -0,0 +1,26 @@
+import { safeGetCanisterEnv } from "@icp-sdk/core/agent/canister-env";
+import { createActor } from "./bindings/backend";
+
+// The ic_env cookie is set by the asset canister (SDK >=0.30.2) on all HTML
+// responses. It contains the replica root key and any PUBLIC_* canister
+// environment variables. In dev mode the vite dev server sets the same cookie
+// via Set-Cookie header (see vite.config.js).
+const canisterEnv = safeGetCanisterEnv();
+
+// Resolve canister ID: cookie (icp-cli + dev server) -> env var (dfx build-time)
+const canisterId =
+  canisterEnv?.["PUBLIC_CANISTER_ID:backend"] ??
+  process.env.CANISTER_ID_BACKEND;
+
+if (!canisterId) {
+  throw new Error(
+    "Canister ID for 'backend' not found. Run 'icp deploy' or 'dfx deploy' first."
+  );
+}
+
+export const backend = createActor(canisterId, {
+  agentOptions: {
+    host: window.location.origin,
+    rootKey: canisterEnv?.IC_ROOT_KEY,
+  },
+});