fix: mf-6820 support red packet on robinhood chain

[swkatmask]

Summary

• MF-6820: the create-red-packet token picker listed the new Robinhood chain (4663), but no V4 contract was registered there, so HAPPY_RED_PACKET_ADDRESS_V4 resolved to undefined → contract hook returned null → the confirm screen silently closed / creation aborted on gas estimation.
• Register the HappyRedPacket V4 contract on Robinhood (deployed by upstream support Robinhood Chain RedPacket#77) and enable the chain for the plugin:
  • packages/web3-constants/evm/red-packet.json: HAPPY_RED_PACKET_ADDRESS_V4 → 0x16f61cb37169523635B6761f3C946892fb3c18fB, HAPPY_RED_PACKET_ADDRESS_V4_BLOCK_HEIGHT → 5036643
  • packages/plugins/RedPacket/src/base.ts: append ChainId.Robinhood to supported chain ids

Verification

• pnpm build + pnpm lint pass.
• On-chain via rpc.mainnet.chain.robinhood.com: encoded the plugin's create_red_packet calldata and eth_estimateGas'd it against the registered address — the call executes inside the contract (reverts only on the contract's own #tokens > #packets validation for a zero total), confirming address + encoding; with real value it stops only at the wallet's zero balance, matching the UI's disabled state.
• Runtime: Lucky Drop dialog renders on Robinhood in the dev extension, picker defaults to the Robinhood network (robinhoodchain.blockscout.com links) and lists native ETH (token list URL 404s, as expected on a new chain).

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
book	Skipped		Sep 9, 2026 12:28pm UTC