Add Etherlink to the explorer contract import networks - #1563
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan includes up to 4 reviews per rolling hour; 2 remain after this review. 📝 WalkthroughWalkthrough
ChangesEtherlink Hypersync support
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This change enables Etherlink contract imports through the explorer path without introducing an actionable merge-blocking risk; it is merge-ready after normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
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 |
Tags Etherlink (42793) as
NetworkWithExploreralongsideHypersyncChain, so it shows up inenvio init contract-import explorer --blockchain.It was tagged
HypersyncChainonly, so the CLI had no explorer import path for Etherlink while HyperSync indexing worked fine.The backend already serves it after enviodev/ui#1199:
returns 200 with the contract name and ABI, so the enum tag was the only blocker.
Came up in etherlinkcom/docs#433 where Etherlink asked whether we index their chain.
Not compiled locally, there is no Rust toolchain on this machine. Nothing matches exhaustively on
NetworkWithExplorer, so CI is the first real check.Summary by CodeRabbit