May 13
Loading video player...
Why does a careful contract surface map make porting from EVM to Solana practical instead of painful? Understanding what state, entry points, and external interactions a contract exposes is the foundation for a successful migration. What you'll learn You will learn how to create a contract surface map that identifies on-chain state, public entry points, and external dependencies to drive your porting plan. The lesson covers techniques for locating storage and stateful counters, mapping EVM APIs and events to Solana program entry patterns, and cataloging oracles and off-chain integrations. You will also learn how to spot gas and compute hotspots that require redesign on Solana's account-based model and how to prioritize components for a staged migration. Concrete examples show translating ERC-20 stakes to SPL token accounts, rewards counters to PDA-owned state accounts, and access control patterns into Anchor constraints. Who this is for Intermediate smart contract developers and engineers familiar with EVM/ Solidity who want to plan and execute a migration to Solana. Assumes basic knowledge of smart contracts and blockchain concepts. Key topics covered - Creating a contract surface map: state, storage, and ownership - Mapping entry points and public APIs from EVM to Solana programs - Identifying external dependencies, oracles, and cross-contract calls - Finding gas/compute hotspots and reworking logic for Solana's model - Prioritization and staged migration strategy Ready to apply these porting techniques to your project? Learn more and continue your Web3 training at https://www.forge.college/