chore: update submodule references and documentation
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
- Marked submodules ai-mcp-pmm-controller, explorer-monorepo, and smom-dbis-138 as dirty to reflect recent changes. - Updated documentation to clarify operator script usage, including dotenv loading and task execution instructions. - Enhanced the README and various index files to provide clearer navigation and task completion guidance. Made-with: Cursor
This commit is contained in:
17
.cursor/rules/chain138-tokens-and-pmm.mdc
Normal file
17
.cursor/rules/chain138-tokens-and-pmm.mdc
Normal file
@@ -0,0 +1,17 @@
|
||||
---
|
||||
description: Canonical cUSDT/cUSDC addresses, DODOPMMIntegration, and PMM pool addresses for Chain 138
|
||||
alwaysApply: true
|
||||
---
|
||||
|
||||
# Chain 138 tokens and PMM — single source of truth
|
||||
|
||||
**Canonical tokens (mint / liquidity / Explorer):** Use only these. Single source: `docs/11-references/EXPLORER_TOKEN_LIST_CROSSCHECK.md` §5 and §8.
|
||||
|
||||
- **cUSDT:** `0x93E66202A11B1772E55407B32B44e5Cd8eda7f22` (6 decimals)
|
||||
- **cUSDC:** `0xf22258f57794CC8E06237084b353Ab30fFfa640b` (6 decimals)
|
||||
|
||||
**DODOPMMIntegration:** `0x79cdbaFBaA0FdF9F55D26F360F54cddE5c743F7D` — on-chain verified 2026-03-04: `compliantUSDT()` / `compliantUSDC()` return the canonical addresses above.
|
||||
|
||||
**PMM pools:** cUSDT/cUSDC `0x9fcB06Aa1FD5215DC0E91Fd098aeff4B62fEa5C8` | cUSDT/USDT `0xa3Ee6091696B28e5497b6F491fA1e99047250c59` | cUSDC/USDC `0x90bd9Bf18Daa26Af3e814ea224032d015db58Ea5`
|
||||
|
||||
**RPC (deploy):** `RPC_URL_138=http://192.168.11.211:8545`. **Deployer:** `0x4A666F96fC8764181194447A7dFdb7d471b301C8`. Add-liquidity reads tokens from the integration contract, not env. Do not use non-canonical Blockscout addresses (§2 of EXPLORER_TOKEN_LIST_CROSSCHECK).
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
description: This machine has LAN and Proxmox access; operator scripts can be run from here
|
||||
description: This machine has LAN and Proxmox access; operator scripts load dotenv and can be run from here
|
||||
alwaysApply: true
|
||||
---
|
||||
|
||||
@@ -7,4 +7,9 @@ alwaysApply: true
|
||||
|
||||
**Remember:** This machine **is** LAN/operator — it has LAN and Proxmox access to 192.168.11.x. Operator scripts **can and should** be run from here when the user asks to run operator tasks.
|
||||
|
||||
When suggesting or running operator/LAN tasks (e.g. `run-all-operator-tasks-from-lan.sh`, contract verification, NPMplus backup, nginx/VMID 5000, token-aggregation DB, E2E checks), assume this host can reach Proxmox hosts (192.168.11.10–12), Chain 138 RPC (192.168.11.211:8545), NPMplus, and Blockscout. Do not treat operator tasks as "unrunnable from this environment" unless a specific credential or network constraint is missing. Only credentials in `.env` (e.g. `NPM_PASSWORD`, `PRIVATE_KEY`) are required to execute them.
|
||||
- **Dotenv:** `run-all-operator-tasks-from-lan.sh` and `run-operator-tasks-from-lan.sh` **always load dotenv** via `scripts/lib/load-project-env.sh` (repo `.env` + `smom-dbis-138/.env`). No need to `source .env` before running.
|
||||
- **Proxmox hosts:** 192.168.11.10 (ML110), .11 (R630-01), .12 (R630-02). Chain 138 RPC: 192.168.11.211:8545.
|
||||
- **NPMplus password:** In **project root** `.env` — variable `NPM_PASSWORD` (with `NPM_EMAIL`, `NPM_URL`). Operator scripts load it via `load-project-env.sh`; NPMplus API: 192.168.11.167:81 or .166:81.
|
||||
- **Continue and complete:** (1) `./scripts/run-completable-tasks-from-anywhere.sh` then (2) `./scripts/run-all-operator-tasks-from-lan.sh` (use `--skip-backup` if NPM_PASSWORD not set; add `--deploy` or `--create-vms` as needed).
|
||||
|
||||
When suggesting or running operator/LAN tasks (e.g. `run-all-operator-tasks-from-lan.sh`, contract verification, NPMplus backup, nginx/VMID 5000, token-aggregation DB, E2E checks), assume this host can reach Proxmox hosts (192.168.11.10–12), Chain 138 RPC, NPMplus, and Blockscout. Credentials in `.env` or `smom-dbis-138/.env` (e.g. `NPM_PASSWORD`, `PRIVATE_KEY`) are used automatically when the operator script runs.
|
||||
|
||||
22
.cursor/rules/project-doc-and-deployment-refs.mdc
Normal file
22
.cursor/rules/project-doc-and-deployment-refs.mdc
Normal file
@@ -0,0 +1,22 @@
|
||||
---
|
||||
description: Master doc references and deployment phases (A–D) for full network coverage
|
||||
alwaysApply: true
|
||||
---
|
||||
|
||||
# Project doc and deployment references
|
||||
|
||||
When answering token/PMM/deployment questions, prefer these docs over inferring from other files. Cite §5 / §8 for canonical and verification.
|
||||
|
||||
**Canonical / verification:** `docs/11-references/EXPLORER_TOKEN_LIST_CROSSCHECK.md` (§5 canonical, §8 on-chain verification)
|
||||
**Contract addresses:** `docs/11-references/CONTRACT_ADDRESSES_REFERENCE.md`
|
||||
**Address matrix:** `docs/11-references/ADDRESS_MATRIX_AND_STATUS.md`
|
||||
**Fixes and deployments:** `docs/00-meta/REQUIRED_FIXES_GAPS_AND_DEPLOYMENTS_LIST.md`
|
||||
**TODOs:** `docs/00-meta/TODOS_CONSOLIDATED.md`
|
||||
**Operator commands:** `docs/00-meta/OPERATOR_READY_CHECKLIST.md`
|
||||
**Doc index:** `docs/MASTER_INDEX.md`
|
||||
|
||||
**Deployment phases (full coverage):** `docs/03-deployment/REMAINING_DEPLOYMENTS_FOR_FULL_NETWORK_COVERAGE.md`
|
||||
- A: mint + add liquidity (138) — `mint-for-liquidity.sh`, AddLiquidityPMMPoolsChain138
|
||||
- B: Celo/Wemix CCIP + LINK (Wemix needs 0.4 WEMIX)
|
||||
- C: `PHASE_C_CW_AND_EDGE_POOLS_RUNBOOK.md`
|
||||
- D: `PHASE_D_OPTIONAL_CHECKLIST.md`
|
||||
Reference in New Issue
Block a user