d-bis/cross-chain-pmm-lps
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: refresh deployment status and solana policies

Browse Source
This commit is contained in:
defiQUG
2026-04-18 12:05:17 -07:00
parent 0b089f1181
commit 5aa162e6b3
6 changed files with 2052 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
scripts/README.md
View File

@@ -31,6 +31,8 @@ Validates `config/deployment-status.json` for minimum viable deployed graph. Use
- If `bridgeAvailable === true` on a chain, `cwTokens` must include at least **cWUSDT** and **cWUSDC** (phase 1).
- For each `pmmPool` and each `pmmPoolsVolatile[]` entry: `role` ∈ {defense, public_routing, truu_routing}; `feeBps` and `k` present; `base`/`quote` (or `tokenIn`/`tokenOut`) exist in `cwTokens` or `anchorAddresses` (e.g. mainnet **TRUU** under `anchorAddresses.TRUU`). Non-zero `poolAddress` must not be the zero address.
- For each `gasReferenceVenues[]` entry: `supported` must be explicit, `aggregatorOnly` is only valid for `1inch`, `supported=false` means the lane is explicitly unsupported (and can never be live), and `supported=true` with `live=false` / `routingVisible=false` means the lane is planned or staged.
- `aggregatorOnly=true` rows are routing overlays, not stand-alone live venues.
**Run:**