@xyo-network/xl1-cli 4.0.0 → 4.0.1

package/README.md

@@ -392,9 +392,9 @@ Explicit `connections` + `providerBindings` overrides.
 }
 ```
 
-### Stateless API
+### Federated API
 
-Read-only API proxying a remote chain RPC.
+Read-only API proxying a remote chain RPC via explicit `providerBindings`.
 
 ```json
 {
@@ -406,12 +406,21 @@ Read-only API proxying a remote chain RPC.
         "url": "https://chain.example.com/rpc"
       }
     },
+    "providerBindings": {
+      "AccountBalanceViewer": { "connection": "default-rpc" },
+      "BlockViewer": { "connection": "default-rpc" },
+      "FinalizationViewer": { "connection": "default-rpc" },
+      "MempoolRunner": { "connection": "default-rpc" },
+      "MempoolViewer": { "connection": "default-rpc" },
+      "TransactionViewer": { "connection": "default-rpc" },
+      "XyoRunner": { "connection": "default-rpc" },
+      "XyoViewer": { "connection": "default-rpc" }
+    },
     "actors": [
       {
         "name": "api",
         "host": "0.0.0.0",
-        "port": 8080,
-        "stateless": true
+        "port": 8080
       }
     ]
   }
@@ -1220,7 +1229,7 @@ If you omit `mnemonic` entirely, the CLI falls back to a built-in dev mnemonic a
 Two CLI flags help you verify what the chain *would* do without actually starting it:
 
 - `xl1 --dump-config start <actors>` — prints the fully resolved config (file + env + CLI flags merged, defaults applied) to stdout, then exits. Secret-bearing fields are redacted by default; pass `--with-secrets` on a developer box to see raw values.
-- `xl1 --dump-providers start <actors>` — runs the locator construction up to the point where actor runners would start, then prints a per-actor tree of every registered provider (implementation class, scope, dependencies). Cross-actor duplicates are flagged with `⚠ also in: ...`. Use this to confirm that, e.g., your stateless API actually picked the JsonRpc tier-3 viewers.
+- `xl1 --dump-providers start <actors>` — runs the locator construction up to the point where actor runners would start, then prints a per-actor tree of every registered provider (implementation class, scope, dependencies). Cross-actor duplicates are flagged with `⚠ also in: ...`. Use this to confirm that, e.g., your federated API actually picked the JsonRpc tier-3 viewers.
 
 ```sh
 xl1 -c ./xyo.json --dump-providers start api producer