May 13
Loading video player...
Struggling to translate an EVM contract's monolithic storage and functions into Solana's accounts-and-programs model? This lesson shows how to convert storage mappings and ownership choices into a concrete Solana architecture before you write any program code. What you'll learn: You will learn how to evaluate tradeoffs between monolithic and modular program structures and pick program decomposition patterns appropriate for porting an EVM contract. The lesson covers account grouping strategies that balance rent-exemption, access locality, and upgradeability, including how to size accounts and use program-derived addresses (PDAs). You will see how to compose instruction-level flows that preserve atomic invariants across multiple accounts and across programs using cross-program invocations (CPI). Finally, we compare serialization approaches and authority delegation patterns to match update frequency and signer models so your redesign is practical and secure. Who this is for: Intermediate developers who understand EVM smart contracts and basic Solana concepts (accounts, programs, PDAs, CPI). Prior experience with contract storage mapping and account sizing is helpful. Key topics covered: - Program decomposition: monolithic vs modular patterns and when to split functionality - Account grouping and sizing: PDAs, program-owned vs externally-owned accounts, and rent-exemption tradeoffs - Instruction composition and atomic flows: designing CPI-based multi-account transactions - Serialization and schema choices: Borsh, compact layouts, and tradeoffs for update frequency - Authority delegation patterns: signer models, multisig, and delegated authorities - Practical sketching: producing a high-level redesign blueprint for an example EVM contract Ready to move from mapping decisions to a Solana-ready design? Start building your port with a clear architecture blueprint: https://www.forge.college/