Bump master for telemtry, in-TEE proto handling, etc.

.github/workflows/ci.yml

@@ -4,9 +4,9 @@ name: CI
 
 on:
   push:
-    branches: [master]
+    branches: [master, develop]
   pull_request:
-    branches: [master]
+    branches: [master, develop]
 
 jobs:
   test:
@@ -31,4 +31,4 @@ jobs:
         run: bunx @biomejs/biome lint .
 
       - name: Run tests
-        run: bun test
+        run: bun test

.gitignore

@@ -36,5 +36,10 @@ build
 /proto/**
 src/proto/*.ts
 src/proto/**/*.ts
+!src/proto/node.descriptor.ts
 
-src/assets/proto/**
+src/assets/proto/**
+
+# Worktrees, Agents
+.codex
+.emdash

AGENTS.md

@@ -0,0 +1,18 @@
+## Agent Orchestrator (ao) Session
+
+You are running inside an Agent Orchestrator managed workspace.
+
+## Source layout (cex-broker)
+
+- `src/server.ts` — gRPC registration and handler wiring only; do not add domain logic here.
+- `src/handlers/` — RPC dispatch (`execute-action/`, `subscribe/`).
+- `src/helpers/` — domain and shared utilities (`shared/`, `grpc/`, `order-book.ts`, etc.).
+- Dependency direction: `server` → `handlers` → `helpers`. Helpers must not import from `server` or `handlers`.
+- Import concrete helper modules (e.g. `helpers/deposit`); avoid growing `helpers/index.ts` with server utilities.
+Session metadata is updated automatically via shell wrappers.
+
+If automatic updates fail, you can manually update metadata:
+```bash
+~/.ao/bin/ao-metadata-helper.sh  # sourced automatically
+# Then call: update_ao_metadata <key> <value>
+```

Dockerfile

@@ -6,6 +6,13 @@ RUN apt-get update -y \
   && apt-get install -y --no-install-recommends ca-certificates curl \
   && rm -rf /var/lib/apt/lists/*
 
-RUN bun install --global @usherlabs/cex-broker@0.2.6
+COPY package.json bun.lock ./
+COPY patches ./patches
+RUN bun install --frozen-lockfile
 
-CMD ["cex-broker"]
+COPY build.ts proto-gen.sh tsconfig.json ./
+COPY scripts ./scripts
+COPY src ./src
+RUN bun run build
+
+CMD ["bun", "./dist/commands/cli.js"]

POLICY.md

@@ -110,7 +110,17 @@ Accepted values:
 - **A network/chain identifier** — e.g. `"ARBITRUM"`, `"BEP20"`, `"ETH"`, `"SOL"`. The value must match what the exchange uses for that chain.
 - **`"*"`** — wildcard; matches any network.
 
-Even if the policy allows a network, the selected exchange must also support that network for the currency or the request will still fail at execution time.
+The broker normalizes common operator aliases before matching policy:
+
+| Operator alias | Broker network id |
+|----------------|-------------------|
+| `ARB`, `ARBITRUM` | `ARBITRUM` |
+| `ETH`, `ERC20`, `ETHEREUM` | `ETHEREUM` |
+| `BNB`, `BSC`, `BEP20` | `BNB` |
+
+Even if the policy allows a normalized network, the selected exchange must also
+support that network for the currency or the request will still fail at
+execution time.
 
 ---
 
@@ -191,6 +201,46 @@ Common rejection reasons:
 - address not whitelisted
 - token not in `coins` for the matched rule
 
+### Narrow Binance/MEXC USDC BEP20 corridor example
+
+Use a dedicated policy for treasury corridors instead of relying on broad
+exchange/network rules. The example
+`policy/policy.binance-mexc-usdc-bep20.example.json` permits only USDC over the
+normalized `BNB` network family (`BNB`, `BSC`, or `BEP20`) between Binance and
+MEXC:
+
+```json
+{
+  "withdraw": {
+    "rule": [
+      {
+        "exchange": "BINANCE",
+        "network": "BEP20",
+        "coins": ["USDC"],
+        "whitelist": ["0x1111111111111111111111111111111111111111"]
+      },
+      {
+        "exchange": "MEXC",
+        "network": "BEP20",
+        "coins": ["USDC"],
+        "whitelist": ["0x2222222222222222222222222222222222222222"]
+      }
+    ]
+  },
+  "deposit": {
+    "rule": [
+      { "exchange": "MEXC", "network": "BEP20", "coins": ["USDC"] },
+      { "exchange": "BINANCE", "network": "BEP20", "coins": ["USDC"] }
+    ]
+  }
+}
+```
+
+This policy does not authorize volatile inventory transfer. If a treasury
+ceremony chooses remote volatile acquisition, that acquired-asset transfer must
+be explicitly requested, live-discovered, policy-approved, cost-gated, and
+attested by the caller.
+
 ---
 
 ## Order policy (`order.rule`)