ccip-router 0.5.1 → 0.5.3

package/README.md

@@ -240,6 +240,23 @@ What `withWyriwe()` adds on top of basic:
 
 ---
 
+## Node modes
+
+ccip-router runs in two modes — any combination can form a mesh.
+
+| Mode | Description | Typical host |
+|---|---|---|
+| **Operator node** | Admin dashboard, signing key, ENS records, attestation pipeline | Self-hosted (Docker / VPS / home server) |
+| **Public node** | Mesh sync + CCIP-Read serving only. No admin surface, no key UI. Set `DISABLE_ADMIN=true` | Any PaaS (Railway, Fly, Render) |
+
+Both modes use the same Docker image and npm package. The difference is configuration only.
+
+**→ [Full deployment guide](DEPLOYMENT.md)** — self-hosted operator setup, Railway one-click public node, reverse proxy config, Cloudflare Tunnel, multi-URL resolver, key generation, security notes.
+
+[![Deploy on Railway](https://railway.com/button.svg)](https://railway.com/template/ccip-router)
+
+---
+
 ## Quick start (setup wizard)
 
 ```bash
@@ -266,6 +283,8 @@ npm run dev
 
 ## Environment variables
 
+> **Security:** never put `GATEWAY_PRIVATE_KEY` or other secrets inline in a compose file. Use `env_file:` pointing to a `chmod 600` file, or your platform's secrets UI (Railway Variables, Fly secrets, etc.). See [DEPLOYMENT.md](DEPLOYMENT.md) for the recommended pattern.
+
 | Variable | Required | Default | Description |
 |---|---|---|---|
 | `GATEWAY_PRIVATE_KEY` | Yes* | — | 32-byte hex signing key (`0x...`). Without it the node runs in dry-run mode (unsigned records). |
@@ -282,6 +301,12 @@ npm run dev
 | `NODE_REGISTRY` | No | — | Deployed `NodeRegistry` contract address. Enables on-chain node registration. |
 | `RPC_URL` | No | — | JSON-RPC endpoint. Required alongside `ATTESTATION_INDEX`. |
 | `MODEL_HASH` | No | — | `keccak256` of model weights CID. Required to activate WYRIWE attestation. |
+| `NODE_URL` | No | — | This node's public URL. Required for VNI (signed node identity). |
+| `AUTO_DISCOVER` | No | `true` | Pull peer lists from synced peers automatically. |
+| `CDN_PROVIDER` | No | — | `pinata` or `storacha`. Enables IPFS upload from admin panel. |
+| `CDN_API_KEY` | No | — | API key / JWT for the configured CDN provider. |
+| `NETWORK_KEY` | No | — | Ethereum address. Messages signed by this key are marked as official network announcements. |
+| `DISABLE_ADMIN` | No | `false` | Set `true` to skip mounting `/admin` and `/static` entirely. Recommended for public PaaS nodes. |
 
 \* Can also come from `config.json` written by the setup wizard.
 
@@ -626,27 +651,6 @@ Tests use `SQLiteDB(':memory:')` directly (bypassing the runtime singleton) and
 
 ---
 
-## Roadmap
-
-### v0.3.0 — IPFS browser resolution
-Native ENS browsers (Brave, eth.link) resolve `contenthash` directly on-chain — they don't follow CCIP-Read. v0.3.0 will add an **IPFS + Browser resolution** admin panel that closes this gap:
-
-- Pin a file or CID to IPFS (via Pinata) from the admin panel
-- Set the resulting CID as the ENS name's `contenthash` on-chain (MetaMask, no stored key)
-- Manage multiple names from one panel
-
-Combined with `withEns()` (CCIP-Read, dynamic records) this makes the gateway handle both resolution paths:
-
-| Path | Who | How |
-|---|---|---|
-| Static pages | Brave / native ENS browsers | `contenthash` on-chain → IPFS |
-| Dynamic data | dapps / smart contracts | `offchainLookup` → CCIP-Read → `withEns()` |
-
-### v0.4.0+ — Phase 2 / Phase 3
-See [GATEWAY_DECENTRALIZATION_PLAN.md](https://github.com/Echo-Merlini/ccip-router) for the full decentralisation roadmap (chain as source of truth, incentivised node network).
-
----
-
 ## Related
 
 - [ens-boiler](https://github.com/Echo-Merlini/ens-boiler) — opinionated ENS agent stack built on `ccip-router`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ccip-router",
-  "version": "0.5.1",
+  "version": "0.5.3",
   "description": "The coordination layer CCIP-Read was missing. Peer sync, deduplication, and cryptographic attestation for any CCIP-Read gateway.",
   "type": "module",
   "main": "./dist/lib.js",