chore: migrate motoko/evm_block_explorer to icp-cli

.github/workflows/evm_block_explorer.yml

@@ -5,6 +5,7 @@ on:
     branches: [master]
   pull_request:
     paths:
+      - motoko/evm_block_explorer/**
       - rust/evm_block_explorer/**
       - .github/workflows/evm_block_explorer.yml
 
@@ -13,6 +14,20 @@ concurrency:
   cancel-in-progress: true
 
 jobs:
+  motoko-evm_block_explorer:
+    runs-on: ubuntu-24.04
+    container: ghcr.io/dfinity/icp-dev-env-motoko:1.0.1
+    env:
+      ICP_CLI_GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+    steps:
+      - uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4.3.1
+      - name: Deploy and test
+        working-directory: motoko/evm_block_explorer
+        run: |
+          icp network start -d
+          icp deploy
+          bash test.sh
+
   rust-evm_block_explorer:
     runs-on: ubuntu-24.04
     container: ghcr.io/dfinity/icp-dev-env-rust:1.0.1

.gitignore

@@ -15,3 +15,4 @@ target/
 mops.lock
 .env
 **/src/declarations/
+**/src/bindings/

motoko/evm_block_explorer/README.md

@@ -1,28 +1,77 @@
-# EVM block explorer
+# EVM Block Explorer
 
-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.
+[View this sample's code on GitHub](https://github.com/dfinity/examples/tree/master/motoko/evm_block_explorer)
 
+## Overview
+
+The EVM Block Explorer example demonstrates how an ICP canister can fetch block data directly from Ethereum and other EVM-compatible chains. Using HTTPS outcalls via the [EVM RPC canister](https://github.com/dfinity/evm-rpc-canister), canisters on ICP can read on-chain data without a bridge or oracle. The same pattern applies to any EVM-compatible chain supported by the EVM RPC canister.
+
+<!--
 ## 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.
+
+[![Open in ICP Ninja](https://icp.ninja/assets/open.svg)](https://icp.ninja/i?g=https://github.com/dfinity/examples/motoko/evm_block_explorer)
+-->
+
+## Build and deploy from the command line
+
+### Prerequisites
+
+- [Node.js](https://nodejs.org/) v18+
+- [icp-cli](https://cli.internetcomputer.org/): `npm install -g @icp-sdk/icp-cli @icp-sdk/ic-wasm`
+- [ic-mops](https://mops.one/): `npm install -g ic-mops`
+
+### Install
+
+Clone the example project:
+
+```bash
+git clone https://github.com/dfinity/examples
+cd examples/motoko/evm_block_explorer
+```
+
+### Deploy and test
 
-[![](https://icp.ninja/assets/open.svg)](https://icp.ninja/i?g=https://github.com/dfinity/examples/motoko/evm_block_explorer)
+Start the local network, deploy all canisters (including the local EVM RPC canister), and run the tests:
 
-## Build and deploy from the command-line
+```bash
+icp network start -d
+icp deploy
+bash test.sh
+icp network stop
+```
 
-### 1. [Download and install the IC SDK.](https://internetcomputer.org/docs/building-apps/getting-started/install)
+To start a frontend dev server with hot reload during frontend development:
 
-### 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/)
+```bash
+npm run dev --prefix frontend
+```
 
-### 3. Navigate into the project's directory.
+### Deploying on ICP mainnet
 
-### 4. Deploy the project to your local environment:
+On mainnet, the `evm_rpc` canister is already deployed at `7hfb6-caaaa-aaaar-qadga-cai`. Deploy only the backend and frontend — icp-cli injects the correct canister ID via the `ic` environment configuration in `icp.yaml`:
 
+```bash
+icp deploy -e ic
 ```
-dfx start --background --clean && dfx deploy
+
+## 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, regenerate the `.did` file:
+
+```bash
+mops generate candid backend
 ```
 
+## RPC providers and API keys
+
+The example uses [PublicNode](https://ethereum-rpc.publicnode.com) by default — a free, no-registration provider that works out of the box locally and on mainnet. This is sufficient for getting started and automated testing.
+
+For production deployments requiring premium providers (Alchemy, Ankr, BlockPi), refer to the [EVM RPC canister documentation](https://github.com/dfinity/evm-rpc-canister) for how to configure API keys. Once configured, change `#EthMainnet(?[#PublicNode])` in `backend/EvmRpcApi.mo` to `#EthMainnet(null)` to use all configured providers for better consensus.
+
 ## 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/guides/security/overview) for developing on ICP. This example may not implement all the best practices.