Skip to content

Fix Robinhood v4 address prediction and vanity for 0x4b07 suffix - #136

Merged
Quazia merged 3 commits into
mainfrom
fix/robinhood-vanity-prediction
Jul 8, 2026
Merged

Fix Robinhood v4 address prediction and vanity for 0x4b07 suffix#136
Quazia merged 3 commits into
mainfrom
fix/robinhood-vanity-prediction

Conversation

@Quazia

@Quazia Quazia commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Point clanker_v4_robinhood at the BSC v4.1 ClankerToken creation bytecode so CREATE2 prediction matches on-chain Robinhood deploys.
  • Fixes the incident mismatch where SDK predicted 0x75b45af4... but the actual token was 0x085844F1....
  • Ensures vanity search (init_code_hash) and predictTokenAddressV4 stay in sync for Robinhood 0x4b07 suffix addresses.

Test plan

  • predictTokenAddressV4 matches Robinhood incident deploy tx fixture (0xab51d3e1...0x085844F1...)
  • Live vanity service returns ...4b07 and prediction matches returned address
  • Base config still uses generic v4 bytecode (regression guard)
  • Merge and publish 4.2.18 to npm

Made with Cursor

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>

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

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_robinhood token bytecode to ClankerToken_v4_bsc_bytecode so 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.

Comment thread test/tokens/v4/clankerV4Token.config.test.ts
Quazia and others added 2 commits July 8, 2026 18:36
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>
@Quazia
Quazia merged commit cf34aca into main Jul 8, 2026
3 checks passed
@Quazia
Quazia deleted the fix/robinhood-vanity-prediction branch July 8, 2026 22:44
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