d-bis/proxmox
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Tighten mainnet PMM bootstrap verification
All checks were successful
Deploy to Phoenix / deploy (push) Successful in 9s
Details

Browse Source
This commit is contained in:
defiQUG
2026-04-14 17:27:39 -07:00
parent cba978f656
commit 6ae8590134
2 changed files with 43 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/04-configuration/MEV_CHAIN138_ALL_MAINNET_ROLLOUT_TRACKER.md
View File

@@ -44,6 +44,11 @@ It is intentionally split into:
- Re-run result after the fix:
- `cWUSDT/cWUSDC` now resolves and reads healthy reserves
- readiness gate now ends with `4 hard failure(s), 0 warning(s)`
- `2026-04-14` `check-mainnet-public-dodo-cw-bootstrap-pools.sh` now passes after
downgrading operator-wallet balance shortages from false failures to warnings.
- Same bootstrap verifier surfaced one env/registry drift:
- registry-authoritative `cWUSDC/USDC` pool is `0x69776fc607e9edA8042e320e7e43f54d06c68f0E`
- some env/default flows still reference legacy pool `0xB227dDA4e89E2EA63A1345509C9AC02644e8d526`
This means Mainnet public PMM operation is not yet in a fully healthy state even
though large parts of the deployment inventory exist.
@@ -146,6 +151,7 @@ though large parts of the deployment inventory exist.
- rebalance `cWUSDC/USDC`
- rebalance `cWUSDT/USDT`
- rebalance `cWUSDC/USDT`
- reconcile remaining legacy `POOL_CWUSDC_USDC_MAINNET` env/default references with the registry-authoritative pool
6. Publish the final ALL Mainnet native venue matrix before trying to wire full MEV discovery there.
## Truthful Completion Condition