Skip to content

deploy(sepolia): redeploy BLS modules for slash unification (#329) + rewire#330

Open
jhfnetboy wants to merge 2 commits into
mainfrom
deploy/new-bls-modules-sepolia
Open

deploy(sepolia): redeploy BLS modules for slash unification (#329) + rewire#330
jhfnetboy wants to merge 2 commits into
mainfrom
deploy/new-bls-modules-sepolia

Conversation

@jhfnetboy

Copy link
Copy Markdown
Member

新 BLSAggregator + DVTValidator(含 #329 的统一 slash 共识)已部署到 Sepolia 并接线。

新地址

合约 地址
DVTValidator 0x568b1486BFE036e603eA11f0D03Dc47fa62c9E0e
BLSAggregator 0xF51c029879685Ced8fbCfa4b647c2eAe50Cd8B13

已链上校验:slashThresholds=2/3/3、slashPolicyAdmin=deployer、dvt↔bls 互相接好。

已完成的链上接线(deployer 是 SP+staking owner)

  • SP.queueBLSAggregator(new) → 24h timelock,ETA 1783356732 · tx 0x93452c28…
  • staking.setAuthorizedSlasher(new, true) · tx 0xd6b61d7c…

待跟进(follow-up)

  • SP.applyBLSAggregator() — 24h 后(ETA 到期)
  • owner:addValidator×3(Jason/Anni/Bob)+ registerBLSPublicKey×3(+slot)+ setSlashPolicyAdmin(多签/TimelockController)
  • staking.setAuthorizedSlasher(old, false) — apply 之后
  • SDK:更新 BLSAggregator/DVTValidator 地址 + ABI

顺带

修正了过时的 07b_DeployBLSModules.s.sol(BLSAggregator 构造器现在拒绝 zero dvtValidator,须先部署 DVTValidator)——本 PR 用新脚本 DeployNewBLSModules.s.sol 正确排序。

https://claude.ai/code/session_01MxPwC3rr4mLTSb3cJtsYMm

…rewire

Redeployed the two non-upgradeable BLS modules with the unified slash consensus
(PR #329) and updated Sepolia addresses + wiring.

New Sepolia addresses:
- DVTValidator:  0x568b1486BFE036e603eA11f0D03Dc47fa62c9E0e
- BLSAggregator: 0xF51c029879685Ced8fbCfa4b647c2eAe50Cd8B13
  (slashThresholds 2/3/3, slashPolicyAdmin = deployer, dvt<->bls wired)

On-chain wiring done (deployer is SP + staking owner):
- SP.queueBLSAggregator(new)  -> 24h timelock, apply after ETA 1783356732
  tx 0x93452c28cc80ec8db2c74cab8cfd99331404b266b40c3642176bc722985cae36
- staking.setAuthorizedSlasher(new, true)
  tx 0xd6b61d7c4519c7b336438f03ed4b5f7e932f59bf631e86c72cd9133305066c18

Pending (follow-up):
- SP.applyBLSAggregator() after 24h
- owner: addValidator x3, registerBLSPublicKey x3 (+slot), setSlashPolicyAdmin(multisig/timelock)
- staking.setAuthorizedSlasher(old, false) after apply
- SDK: update BLSAggregator/DVTValidator address + ABI

Fixes stale 07b_DeployBLSModules.s.sol ordering (BLSAggregator constructor now
rejects zero dvtValidator, so DVTValidator must deploy first).

Claude-Session: https://claude.ai/code/session_01MxPwC3rr4mLTSb3cJtsYMm
@jhfnetboy jhfnetboy requested a review from fanhousanbu as a code owner July 5, 2026 16:54
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

…Aggregator

Codex: config was ahead of active wiring — it listed the NEW BLS module addresses,
but SP.BLS_AGGREGATOR is still the OLD aggregator during the 24h queue/apply timelock,
so a slash driven through the new aggregator would revert at SP.

Fix: revert config.sepolia.json to the OLD (currently-active) addresses and record
the NEW deployed-but-pending addresses + txs + apply-ETA + ordered follow-up in
deployments/pending-bls-migration-sepolia.md. Flip config to the new addresses only
after SP.applyBLSAggregator() (step 2 of the follow-up).

Claude-Session: https://claude.ai/code/session_01MxPwC3rr4mLTSb3cJtsYMm
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