Files

Deploy to Phoenix / deploy (push) Has been cancelled

Details

docs: update master documentation and push to Gitea (2026-03-06)

- MASTER_INDEX: Last Updated 2026-03-06; status 59/59 contracts; add NEXT_STEPS_LIST, CONTRACT_NEXT_STEPS_LIST
- docs/README, NEXT_STEPS_INDEX, 06-besu/MASTER_INDEX: Last Updated 2026-03-06
- Contract check script: 59 addresses (PMM, vault/reserve, CompliantFiatTokens); canonical CCIP/router
- New docs: EXECUTION_CHECKLIST, NEXT_STEPS_LIST, DOTENV_AUDIT, ADDITIONAL_PATHS, deployer gas runbook, WEMIX_ACQUISITION_TABLED, etc.
- Config: deployer-gas-routes, cro-wemix-swap-routes, routing-registry, token-mapping
- Scripts: check-contracts-on-chain-138, check-pmm-pool-balances-chain138, deployer-gas-auto-route, acquire-cro-and-wemix-gas
- Operator rule: operator-lan-access-check.mdc

Made-with: Cursor

2026-03-06 19:11:25 -08:00

2.3 KiB

Raw Blame History

Wemix (1111) deployments — tabled

Last Updated: 2026-03-06
Status: All Wemix network deployments (CCIP bridges, config, LINK funding on 1111) are tabled until the deployer can acquire WEMIX for gas.

Reason

Deployer needs ~0.4 WEMIX (native gas) on chain 1111 to deploy and configure CCIP bridges.
There is no in-repo route (aggregator/DEX integration or script) to swap ETH, BNB, or Polygon (POL) to WEMIX.
TOKENS_AND_NETWORKS_MINTABLE_TO_DEPLOYER lists Wemix as “Bridge/DEX” only — i.e. manual acquisition.

Options to un-table

Manual acquisition: Use a third-party aggregator (e.g. SwapSpace, ChangeNOW) to swap ETH/BNB/POL to WEMIX and send to the deployer address on 1111. Then run deploy-bridges-config-ready-chains.sh wemix and complete-config.
In-repo route: Implement or integrate an aggregator/DEX route (e.g. LiFi, Jumper, or chain 1111 DEX) that can swap ETH/BNB/POLY → WEMIX and credit the deployer; then document and run the same deploy/config steps. Placeholder script: scripts/deployment/wemix-acquire-via-lifi.js (outputs manual instructions and deployer address; extend when LiFi/Jumper support 1111).

Deployer gas auto-route: The orchestrator ./scripts/deployment/deployer-gas-auto-route.sh includes Wemix (1111): when run, it prints manual instructions and links for WEMIX acquisition. See DEPLOYER_GAS_AUTO_ROUTE_RUNBOOK.md.

What remains tabled

B.2 Wemix CCIP bridges (deploy-bridges-config-ready-chains.sh wemix, complete-config 138↔1111).
Any Phase C/D work that depends on Wemix (cW* or edge pools on 1111).
Wemix token verification and production use until bridges are deployed.

References

REMAINING_DEPLOYMENTS_FOR_FULL_NETWORK_COVERAGE.md — Phase B.2, routing context.
CONFIG_READY_CHAINS_COMPLETION_RUNBOOK — steps when Wemix is un-tabled.
WEMIX_TOKEN_VERIFICATION.md — token addresses on scan.wemix.com.

2.3 KiB Raw Blame History