# Wemix (1111) deployments — tabled

**Last Updated:** 2026-03-06  
**Status:** Historical gas-blocking memo. The deployer now has native WEMIX gas and the bridge contracts are deployed; the remaining blocker is LINK funding plus a successful proof transfer on `1111`.

---

## Reason

- This document recorded the earlier state where the deployer lacked native WEMIX gas.
- Current operator state has native WEMIX gas available and deployed `CCIPWETH9_BRIDGE_WEMIX` / `CCIPWETH10_BRIDGE_WEMIX`.
- The remaining live blocker is that the WEMIX bridge contracts still hold `0 LINK`, so CCIP execution cannot be promoted to live yet.

---

## Options to un-table

1. **Fund LINK on the deployed bridges:** top up `CCIPWETH9_BRIDGE_WEMIX` and `CCIPWETH10_BRIDGE_WEMIX` with enough LINK for operational CCIP fees.
2. **Prove the lane:** run a small `138 -> 1111` bridge transfer and record the receipt as the promotion artifact.
3. **Only if gas drops again:** use a third-party aggregator (e.g. [SwapSpace](https://swapspace.co/exchange-pairs/wemix-bnb), [ChangeNOW](https://changenow.io/currencies/wemix-main/polygon-matic)) to top up native WEMIX.

**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](DEPLOYER_GAS_AUTO_ROUTE_RUNBOOK.md).

---

## What remains tabled

- LINK funding on the deployed WEMIX bridges.
- A successful `138 -> 1111` bridge proof transfer.
- Any Phase C/D work that depends on a fully live `1111` lane (cW* rollout or edge pools on Wemix).

---

## References

- [REMAINING_DEPLOYMENTS_FOR_FULL_NETWORK_COVERAGE.md](REMAINING_DEPLOYMENTS_FOR_FULL_NETWORK_COVERAGE.md) — Phase B.2, routing context.
- [CONFIG_READY_CHAINS_COMPLETION_RUNBOOK](../07-ccip/CONFIG_READY_CHAINS_COMPLETION_RUNBOOK.md) — steps when Wemix is un-tabled.
- [WEMIX_TOKEN_VERIFICATION.md](../07-ccip/WEMIX_TOKEN_VERIFICATION.md) — token addresses on scan.wemix.com.