REVM Source Code - Frame Part 1

Foreword The previous series of articles was meant to quickly walk through the flow, giving everyone a conceptual understanding of REVM. Making source code reading less intimidating. Many details and concepts were skipped. In subsequent articles, we'll try to cover things in more detail. I'll also try to explain Rust syntax where I can. Rust generics are truly headache-inducing — for a beginner like me, it's practically hieroglyphics. I have to research and understand things before I can write about them. Of course, I'll try to ensure accuracy. Frame contains several other EVM classes. We'll cover them in this chapter as well. Purpose Much of Frame's source code was already introduced in Flow(4). In the flow articles, we covered the execution process of make_call_frame and make_create_frame. Both functions create Frames for executing contracts. In REVM, a Frame is created for every contract call. Simple transfers between EOA accounts don't create a Frame. Contract-to-contract calls (CA