reference

mainnet addresses

lode deployment to ethereum mainnet, addresses below. canonical deployment artifact: deployments/1.json in the public repo.

core contracts

lodeToken 0xAdaF95906C05C5c5de12DB00A38e0B02d7Ffd5E9 verified ✓ etherscan ↗
lodeHook 0x8f24193CC75Fc64A30a038442BcD622FF4070088 verified ✓ etherscan ↗
lodeProtocolVault 0x7C5992f48EFB6B8Bf58c7CB608C47c330CFF00F5 verified ✓ etherscan ↗
lodeStaking 0xc499ec42CFEa1fC5c40DCE516A62B6b129228c5A verified ✓ etherscan ↗
lodeFactory 0x5688b988D8d2Ab6F237c9A9f06A524A5878390B9 verified ✓ etherscan ↗

flagship splitter

weth/usdc splitter 0x7201D941b5178cdFA796ffF4562cD8F102926281 verified ✓ etherscan ↗

governance

owner safe (3-of-5) 0x981F445353D5D0624eF39f4F9289367eAe67b0F4 verified ✓ etherscan ↗
guardian safe (1-of-3) 0x0000000000000000000000000000000000000000 verified ✓ etherscan ↗
keeper hot wallet 0x0000000000000000000000000000000000000000 verified ✓ etherscan ↗
buyback executor (eoa) 0x0000000000000000000000000000000000000000 verified ✓ etherscan ↗

burn destination

burn address 0x000000000000000000000000000000000000dEaD verified ✓ etherscan ↗
!
addresses are placeholders

the protocol, splitter, and owner-safe addresses above are live mainnet deployments and verified on etherscan. guardian, keeper, and buyback-executor addresses remain zero-padded until those operational wallets are rotated in. the lodeHook address ends in 0x...88 to satisfy the v4 hook flag bit pattern.

verifying a deployment

each deployed contract is auto-verified on etherscan by the deploy script. cross-check:

  1. the bytecode hash on etherscan matches the build output in build/contracts/.
  2. the constructor arguments match those documented in deployments/1.json.
  3. the hook address bit pattern: (addr & 0x3fff) == 0x88.