Deploying the first API boundary nodes

Governance
9

bc1-dll02.blockchaindevlabs.com is the domain of an API boundary node and icp0.io is a domain of today’s boundary nodes.

I guess that doesn’t really help much. So what does it mean:
We are redesigning the edge of the Internet Computer. Today, there are boundary nodes (or “today’s boundary nodes”) and they do mainly two things:

  1. translate your browser’s HTTP requests into API calls;
  2. route API calls to the right subnet and replica.

This is what is running under icp0.io and ic0.app. These domains serve both purposes: you can directly access canisters using CANISTER_ID.icp0.io and you can directly submit API calls using icp0.io/api/v2/....

The new edge will, at a very high level, split today’s boundary nodes into two entities: API boundary nodes and HTTP gateways. API boundary nodes only serve the API endpoints, while the HTTP gateways mainly provide the capability to access canisters directly from your browser.

Ultimately, bc1-dll02.blockchaindevlabs.com/api/v2/... serves the same purpose as icp0.io/api/v2....

For more information about the new edge of the Internet Computer, check this thread about the boundary node roadmap.

2 Likes