d-bis/smom-dbis-138
4
0
Fork 0
Code Issues Pull Requests 3 Actions Packages Projects Releases Wiki Activity

docs(ccip): document fund-ccip --cap-to-deployer for deployer-only LINK

Browse Source 
Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
defiQUG
2026-05-11 16:12:14 -07:00
parent 01e0779a3d
commit e279443e1c
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/deployment/CCIP_BRIDGE_DESTINATIONS_AND_LINK_FUNDING.md
View File

@@ -86,7 +86,7 @@ Repeat for each destination chain (BSC, Polygon, Base, Optimism, Avalanche, Cron
1. Get LINK on the same chain as the bridge (e.g. from an exchange or faucet).
2. Transfer LINK to the **bridge contract address** (the same address you use for `addDestination`), or use any approved mechanism (e.g. admin top-up function if the contract has one).
- **LINK token addresses** per chain are in `.env` (e.g. `CCIP_GNOSIS_LINK_TOKEN`, `CCIP_ETH_LINK_TOKEN`, etc.) and on [Chainlink CCIP Supported Networks](https://docs.chain.link/ccip/supported-networks).
- **Script:** Run `scripts/deployment/fund-ccip-bridges-with-link.sh` to send LINK to all CCIP bridges (sources .env; set `--link amount, default 10 LINK; use --dry-run` to print commands only).
- **Script:** Run `scripts/deployment/fund-ccip-bridges-with-link.sh` to send LINK to all CCIP bridges (sources `.env`). Flags: `--link <amount>` (default 10 LINK), `--dry-run` (print `cast` only), **`--cap-to-deployer`** (per chain: each bridge gets `min(--link, deployer_balance // bridges_on_chain)` so you can use only deployer LINK without matching 10 LINK on every chain). See script header in `scripts/deployment/fund-ccip-bridges-with-link.sh`.
---