Fix invalid WETH address and wrong BNB explorer links in competition rules - #652
Fix invalid WETH address and wrong BNB explorer links in competition rules#652KaiserSnipes wants to merge 1 commit into
Conversation
…rules - Base baseline: the WETH explorer link pointed to a 39-character (invalid) address; corrected to the canonical Base WETH 0x4200000000000000000000000000000000000006 (on-chain symbol() returns WETH). - BNB baseline: four explorer links pointed at bnbscan.com rather than the canonical BNB Chain explorer (bscscan.com). Addresses unchanged.
|
@KaiserSnipes is attempting to deploy a commit to the cow Team on Vercel. A member of the Team first needs to authorize it. |
|
All contributors have signed the CLA ✍️ ✅ |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe competition rules documentation now uses the canonical Base WETH address and ChangesToken link corrections
Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
I have read the CLA Document and I hereby sign the CLA |
Description
Two link fixes in the competition rules baseline-token sections. The Base chain baseline links WETH to
0x420000000000000000000000000000000000000, which is 39 hex characters and not a valid address. The BNB chain baseline's four explorer links point at bnbscan.com rather than the canonical BNB Chain explorer (bscscan.com).Changes
0x4200000000000000000000000000000000000006(on-chainsymbol()returnsWETH).Summary by CodeRabbit