Skip to content

chore(injective): record the mainnet addresses this config deployed - #5

Merged
danvaneijck merged 1 commit into
injectivefrom
chore/injective-mainnet-deployed-addresses
Sep 8, 2026
Merged

chore(injective): record the mainnet addresses this config deployed#5
danvaneijck merged 1 commit into
injectivefrom
chore/injective-mainnet-deployed-addresses

Conversation

@danvaneijck

Copy link
Copy Markdown
Member

Fills script/config/injective-mainnet.json with the addresses this config produced on chain 1776, as each one landed.

vault 0xB67dd13b30ed21310be170968301eF83827B1Cad
clPoolManager 0x6A4085Bb379e5213Df84Dc2dD52562559602b029
binPoolManager 0xfc6dd227f928Bf3396ff38Da00e19718f9CE7d7e
clPoolManagerOwnerContract 0xaA0F1DCF66E8E7b25c2eb5c59c3c23d982815BF5
binPoolManagerOwnerContract 0x1cBfBEDEB87a474d8b8fb777F463dC050Efb33dA

All five are CREATE3 and all five landed on the addresses predicted from salt + factory before the factory existed. Each was confirmed with eth_getCode and its wiring read back: both pool managers report the vault and are registered on it, and both owner contracts report their pool manager.

clProtocolFeeController / binProtocolFeeController stay "0x" on purpose — Choice deploys its own ChoiceFeeController instead of upstream's stock one, so scripts 04 and 05 here are not run.

Addresses only; no other change.

🤖 Generated with Claude Code

Filled in as each contract landed on chain 1776. Only addresses; every
one was confirmed to have code before being written here.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@danvaneijck
danvaneijck merged commit 34cf265 into injective Sep 8, 2026
3 checks passed
@danvaneijck
danvaneijck deleted the chore/injective-mainnet-deployed-addresses branch September 8, 2026 20:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant