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

Add mainnet checkpoint stack: ISO attestation, participant Etherscan surface, and services.
Some checks failed
CI/CD Pipeline / Solidity Contracts (push) Failing after 1m3s
Details
CI/CD Pipeline / Security Scanning (push) Successful in 2m18s
Details
CI/CD Pipeline / Lint and Format (push) Failing after 34s
Details
CI/CD Pipeline / Terraform Validation (push) Failing after 20s
Details
CI/CD Pipeline / Kubernetes Validation (push) Successful in 22s
Details
Deploy ChainID 138 / Deploy ChainID 138 (push) Failing after 40s
Details
HYBX OMNL TypeScript & anchor / token-aggregation build + reconcile artifact (push) Failing after 49s
Details
OMNL reconcile anchor / Run omnl:reconcile and upload artifacts (push) Failing after 21s
Details
Validation / validate-genesis (push) Successful in 25s
Details
Validation / validate-terraform (push) Failing after 21s
Details
Validation / validate-kubernetes (push) Failing after 8s
Details
Validation / validate-smart-contracts (push) Failing after 8s
Details
Validation / validate-security (push) Failing after 1m11s
Details
Validation / validate-documentation (push) Failing after 14s
Details
Verify Deployment / Verify Deployment (push) Failing after 45s
Details

Browse Source 
Ship AddressActivityRegistry V1/V2, ISO20022IntakeGateway, Chain138ParticipantSurface,
checkpoint hub contracts, checkpoint-core package, aggregator/indexer/sdk services,
relay profile guards, M00 diamond bridge facet, and OMNL compliance contracts.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
defiQUG
2026-05-25 00:30:45 -07:00
parent 9a83aa2034
commit c336809676
326 changed files with 21108 additions and 334 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

@@ -87,6 +87,8 @@ Repeat for each destination chain (BSC, Polygon, Base, Optimism, Avalanche, Cron
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`). 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`.
- **Operator ladder (recommended):** `./scripts/deployment/run-bridge-lane-funding-ladder.sh --execute` — Gnosis LI.FI, mainnet acquire, mainnet CCIP (Celo/Wemix), direct `fund-ccip` transfers.
- **Chain 138 custom CCIP router:** `CCIPRouter.sol` on Chain 138 is **event-only** — `ccipSend` records `MessageSent` and collects LINK fees but **does not deliver** `tokenAmounts` to destination chains. Do **not** use `FundBridgeLinkViaCcip138` / `bridge-link-via-chain138-*.sh` for operator bridge funding until a full token-delivery router is deployed. Preflight: `scripts/verify/verify-chain138-ccip-router-token-delivery.sh`.
---