chore(deployments): record FeeOnTransferDetector on Robinhood, Arc, Avalanche, World Chain and Blast - #171
Open
david-uniswap wants to merge 2 commits into
Open
chore(deployments): record FeeOnTransferDetector on Robinhood, Arc, Avalanche, World Chain and Blast#171david-uniswap wants to merge 2 commits into
david-uniswap wants to merge 2 commits into
Conversation
…valanche, World Chain and Blast Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Records the 5 FeeOnTransferDetectors I deployed today in
deployments/json. These were the only live chains without one. They're getting wired into Uniroute in Uniswap/backend#14301 (ROUTE-2128).0xFdf682F51FE81Aa4898F0AE2163d8A55c127fbC70x8bcEaA40B9AcdfAedF85AdF4FF01F5Ad6517937f0xB99894Da8066B106D66929Be879D3A05B4F595C40x89e5DB8B5aA49aA85AC63f691524311AEB649eba0x693497d35E34F188b8dA1F5F952bE603e289Bf900x9e5A52f57b3038F1B8EeE45F28b3C1967e22799C0x693497d35E34F188b8dA1F5F952bE603e289Bf900x5C69bEe701ef814a2B6a3EDD4B1652CB9cc5aA6f0x693497d35E34F188b8dA1F5F952bE603e289Bf900x5C346464d33F90bABaf70dB6388507CC889C1070forge createfrom this repo's util-contractsFeeOnTransferDetectorat 047d585 (same initcode as the briefcase deployer). The three chains share an address because the deployer was at the same nonce on each.latestplus an appendedhistoryentry withinitcodeHash(keccak of the deploy tx input, no 0x) and the_factoryV2constructor input. Timestamps come from the deploy blocks.initcodeHashis identical to HyperEVM's Deploy-all record (1772a579…) because both use the same v2 factory address, so this build is byte-for-byte the same as the briefcase one..mdfiles are already behind the JSON on main (SwapProxy / ReservesLens aren't in them), and regenerating them pulls in unrelated churn.🤖 Generated with Claude Code