Add migration guide for Ethereum contracts (new IA) #1114
Conversation
nhussein11
added
B0 - Needs Review
There was a problem hiding this comment.
Pull Request Overview
This PR adds a comprehensive migration guide for Ethereum developers moving smart contracts to Polkadot Hub. The guide covers both REVM and PolkaVM backends, explaining when to use each and what changes may be required.
Key changes:
- New migration guide document covering FAQs and considerations for Ethereum contract migration
- Documentation of backend-specific requirements (REVM vs. PolkaVM)
- Guidance on factory contracts, gas costs, and development tooling
Reviewed Changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| smart-contracts/for-eth-devs/migration.md | New migration guide replacing TODO placeholder with comprehensive content on migrating Ethereum contracts to Polkadot Hub |
| llms.txt | Updated to include new migration guide entry and removed erroneous Python package license reference |
| llms-full.txt | Regenerated AI file with full migration guide content and removed Python package license content |
| llms-files/llms-smart-contracts.txt | Regenerated smart contracts AI file with migration guide content |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| Before migrating your contracts, review this checklist: | ||
|
|
||
| - Standard ERC-20, ERC-721, ERC-1155 tokens work without changes. | ||
| - DeFi protocols, DEXs, and AMMs migrate seamlessly. | ||
| - DAOs and governance contracts are fully compatible. | ||
| - Most Solidity contracts deploy identically to Ethereum. | ||
| - Factory contracts using PVM bytecode need pre-uploaded dependencies. | ||
| - Contracts using `EXTCODECOPY` for runtime manipulation require review (for projects that will use PVM bytecode, not EVM bytecode). | ||
| - Replace `transfer()` and `send()` with proper reentrancy guards (for projects that will use PVM bytecode, not EVM bytecode). |
There was a problem hiding this comment.
So this is framed as a checklist, like these are tasks, but "Standard ERC-20, ERC-721, ERC-1155 tokens work without changes" isn't a task, it's a statement. So we need to reframe this.
There was a problem hiding this comment.
The list items should all align, they should all either be tasks or they should all either be statements.
If we need to split this up into two sections, like "Considerations" and "Migration checklist" that could work
| ### Which Solidity features are not supported? | ||
| For REVM, Solidity features are supported. |
There was a problem hiding this comment.
This is a weird statement, like which Solidity features? That's what the question is asking. All of them?
| ### Can I use my existing development tools? | ||
| Yes! Both backends support: |
There was a problem hiding this comment.
| Yes! Both backends support: | |
| Yes. Both backends support: |
Closes 1022
📝 Description
Provide a clear and concise description of your changes.
🔍 Review Preference
Choose one:
🤖 AI-Ready Docs
If content changed, regenerate AI files:
python3 scripts/generate_llms.py✅ Checklist