Files

defiQUG dbd517b279 Sync workspace: config, docs, scripts, CI, operator rules, and submodule pointers.

- Update dbis_core, cross-chain-pmm-lps, explorer-monorepo, metamask-integration, pr-workspace/chains
- Omit embedded publish git dirs and empty placeholders from index

Made-with: Cursor

2026-04-12 06:12:20 -07:00

2.9 KiB

Raw Blame History

Wemix (1111) deployments — tabled

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

Reason

Current deployer: 0x4A666F96fC8764181194447A7dFdb7d471b301C8.
Current preflight status from cd smom-dbis-138 && ./scripts/deployment/preflight-config-ready-chains.sh wemix: RPC OK on chain 1111, deployer balance 0 WEMIX, required minimum 0.4 WEMIX.
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.
Historical DeployWETHBridges.s.sol broadcast files exist for chain 1111, but the recorded bridge addresses do not currently resolve to bytecode on-chain. Treat the Wemix bridge layer as undeployed until a fresh funded deployment succeeds.

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.
CONTRACT_ADDRESSES_REFERENCE.md — current gas-native rollout and Wemix bridge note.

2.9 KiB Raw Blame History