Skip to content

docs: update README with v1.9.0 deployment addresses#1728

Open
ypatil12 wants to merge 2 commits intomainfrom
feat/v1.9.0
Open

docs: update README with v1.9.0 deployment addresses#1728
ypatil12 wants to merge 2 commits intomainfrom
feat/v1.9.0

Conversation

@ypatil12
Copy link
Contributor

Motivation:

The v1.9.0 release has been deployed across mainnet, base, sepolia, hoodi, and base sepolia. The README needs to reflect the updated version references and new implementation addresses for all contracts.

Modifications:

  • Updated all environment version references from v1.8.1/v1.9.0-rc.0 to v1.9.0
  • Updated all contract source code links from older versions (v1.3.0, v1.6.0, v1.8.1) to v1.9.0
  • Updated implementation addresses for all core contracts (DelegationManager, StrategyManager, EigenPodManager, AVSDirectory, RewardsCoordinator, PermissionController, AllocationManager)
  • Added new ProtocolRegistry contract entry
  • Updated implementation addresses for all strategies, EigenPod, EigenStrategy, tokens, AVS contracts, multichain contracts, and PauserRegistry
  • Updated Base deployment addresses and added new contracts (ProtocolRegistry, OperatorTableUpdater, ECDSACertificateVerifier, BN254CertificateVerifier, KeyRegistrar)
  • Updated testnet (Sepolia, Hoodi, Base Sepolia) deployment addresses

Result:

README accurately reflects the current v1.9.0 deployment state across all networks.

@claude
Copy link

claude bot commented Feb 12, 2026

Claude encountered an error after 1m 26s —— View job


Reviewing v1.9.0 deployment address updates

Tasks

  • Read and understand the changed files
  • Review version reference consistency
  • Review deployment address updates and formatting
  • Check typos-cli.toml changes
  • Provide final review feedback

Copy link
Collaborator

@nadir-akhtar nadir-akhtar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Spot checked against internal doc, LGTM

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.

2 participants