Fix Robinhood v4 address prediction and vanity for 0x4b07 suffix - #136
Merged
Conversation
Robinhood deploys BSC v4.1 ClankerToken creation bytecode, so prediction and vanity init_code_hash must use that bytecode instead of the generic v4 artifact. Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR aligns Robinhood v4 CREATE2 token address prediction (and the vanity init_code_hash flow) with on-chain deployments by updating the Robinhood clanker_v4 token creation bytecode to the BSC v4.1 ClankerToken bytecode, and adds regression/fixture tests to prevent future drift.
Changes:
- Update
clanker_v4_robinhoodtoken bytecode toClankerToken_v4_bsc_bytecodeso CREATE2 predictions match Robinhood deploys. - Add on-chain fixture coverage for
predictTokenAddressV4(Robinhood incident tx) plus a Base regression guard. - Add a Robinhood vanity config test, and bump version/changelog for release.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| test/tokens/v4/predictTokenAddressFixtures.test.ts | Adds fixture-based tests to validate CREATE2 prediction against Robinhood incident deploy and ensure Base remains on generic v4 bytecode. |
| test/tokens/v4/clankerV4Token.config.test.ts | Adds a Robinhood vanity-path test to validate converter behavior when vanity: true. |
| src/utils/clankers.ts | Switches Robinhood v4 token creation bytecode to the BSC v4.1 bytecode to keep prediction/vanity in sync with chain reality. |
| package.json | Bumps package version to 4.2.18 for release. |
| CHANGELOG.md | Documents the Robinhood v4 CREATE2 prediction fix in 4.2.18. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Vanity addresses end with b07 per the shared 0x4b07 suffix convention used across v3/v4 tests. Co-authored-by: Cursor <cursoragent@cursor.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.
Summary
clanker_v4_robinhoodat the BSC v4.1ClankerTokencreation bytecode so CREATE2 prediction matches on-chain Robinhood deploys.0x75b45af4...but the actual token was0x085844F1....init_code_hash) andpredictTokenAddressV4stay in sync for Robinhood0x4b07suffix addresses.Test plan
predictTokenAddressV4matches Robinhood incident deploy tx fixture (0xab51d3e1...→0x085844F1...)...4b07and prediction matches returned address4.2.18to npmMade with Cursor