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

4.8 KiB

Raw Blame History

GRU V2 Deployer Funding Status

Last Updated: 2026-04-03
Purpose: Canonical operator reference for the deployer wallet funding posture that still gates the remaining GRU v2 public rollout work.

Canonical verifier

Run:

bash scripts/verify/check-gru-v2-deployer-funding-status.sh

Machine-readable:

bash scripts/verify/check-gru-v2-deployer-funding-status.sh --json

This verifier complements the rollout queue and protocol status surfaces:

Current wallet state

Deployer:

0x4A666F96fC8764181194447A7dFdb7d471b301C8

Observed after the latest funding and route checks on 2026-04-03 (Mainnet route txs finalized 2026-04-04 UTC):

Mainnet: 0.001216982 ETH
Mainnet WETH: 0.005
Mainnet LINK: 0.1171400175
Cronos: 28.8106257165 native
Arbitrum: 0.000775448 ETH
Chain 138 native: 989,399,860.565456 ETH
Chain 138 WETH: 22,845.815258
Chain 138 WETH10: 0.047131
Chain 138 LINK: 994,714.509915
Chain 138 cUSDT: 697,178,939.09
Chain 138 cUSDC: 698,412,990.30

The verifier now prefers the stable public RPC https://rpc-http-pub.d-bis.org because https://rpc.public-0138.defi-oracle.io is currently returning 502 and can produce false “empty wallet” readings.

Funding blockers this creates

1. Arbitrum deploy gas remains below the repo threshold

The existing deployer-balance checker already treats Arbitrum as underfunded for fresh deployment work at the repo threshold of about 0.44 ETH.

2. Mainnet gas is still limited for follow-on public deployment work

Mainnet is no longer near-zero, but 0.001216982 ETH is still a tight operational balance for repeated public deployment and bridge-repair work.

3. Public Mainnet `WETH9` fan-out is blocked by route health, not just gas

Even with enough Mainnet-side WETH and LINK to test the hub route, the live Mainnet -> Arbitrum send from MAINNET_CCIP_WETH9_BRIDGE=0xc9901ce2Ddb6490FAA183645147a87496d8b20B6 failed on tx 0x97df657f0e31341ca852666766e553650531bbcc86621246d041985d7261bb07.

The failure is not a wallet-balance issue:

WETH allowance was set
LINK allowance was set
WETH and LINK balances were unchanged after the failed send except for gas

Tracing shows the revert occurs inside Mainnet router 0x80226fc0Ee2b096224EeAc085Bb9a8cba1146f7D before any bridge event is emitted.

Read-only calculateFee() preflights now also revert for the tracked public-chain selectors BSC, Avalanche, Gnosis, Cronos, Celo, Polygon, Arbitrum, Optimism, and Base, so this should be treated as a broader Mainnet WETH9 public fan-out blocker rather than an Arbitrum-only symptom.

4. Chain 138 is funded, but only when checked against the stable public RPC

Chain 138 is not currently a funding blocker for canonical liquidity or gas operations when read through https://rpc-http-pub.d-bis.org.

This is particularly relevant for the canonical DODO-backed funding surfaces documented in:

Cronos is also clearly funded today.

What this does and does not block

Blocked by current funding

Arbitrum deployer-funded deployment work
follow-on public-chain pool/protocol deployment work that expects comfortable Mainnet gas from the deployer wallet
public-chain funding or deployment work that assumes the current Mainnet WETH9 fan-out leg is live

Not blocked by current funding

fresh Chain 138 deployer-funded liquidity actions
repo/documentation/explorer updates
verifier generation and status publication
read-only RPC checks
planning and queue refinement

Recommended order

Repair or replace the current Mainnet WETH9 source bridge/router path before planning any new hub-based public-chain top-up from Mainnet.
Fund Arbitrum deploy gas to at least the repo threshold before any new Arbitrum deployment branch.
Top up Mainnet gas before beginning repeated public cW* pool and protocol deployment work there.
Keep using the stable Chain 138 public RPC for funding reads until rpc.public-0138.defi-oracle.io is healthy again.

4.8 KiB Raw Blame History