chore(deployments): drop Arbitrum timelock record (not an NTT endpoint)#53
Merged
Conversation
Arbitrum has no NttManager deployed and the WCT token minter is unset (0x0), so it is not a live NTT bridge endpoint — the timelock recorded for it in the previous change was unnecessary. Revert the Arbitrum-specific parts: - Remove the Timelock entry from deployments/42161.json. - Remove Arbitrum from the deployment-docs generator chain list. - Regenerate DEPLOYMENT_ADDRESSES.md to drop the Arbitrum section. Base timelock record + the Optimism LockedTokenStaker doc sync are unaffected. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Claude finished @rplusq's task in 57s —— View job Review
✅ No issues found The change is clean and internally consistent:
Data classification: no sensitive data in diff (all addresses are public on-chain). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reverts the Arbitrum-specific parts of the previous timelock-records change.
Why: Arbitrum has no NttManager deployed and the WCT token's
minter()is unset (0x0) — verified on live Arbitrum. It is not a functional NTT bridge endpoint (unlike Base and mainnet, which have the manager wired and minter set), so recording a timelock deployment for it was unnecessary.Changes
Timelockentry fromdeployments/42161.json.DEPLOYMENT_ADDRESSES.md— drops the Arbitrum section.Unaffected: the Base timelock record and the Optimism
LockedTokenStakerdoc sync remain.Note: a
Timelockcontract was deployed on Arbitrum before this decision; it is inert (owns nothing, holds no roles over the token) and is simply left unused. No on-chain action is needed.🤖 Generated with Claude Code