In the previous post we have created and compiled a simple contract. We have seen the output from the compiler, but have not done anything with it, since I told you I would get back to it. Well, here I am, let’s look at the bytecode and see what it does, what it means and how it is interpreted. Bytecode Now, I have talked a few times about 'bytecode' without really explaining what it is or what it does.

These days many developers use tools like hardhat or truffle to compile, test and deploy their smart contracts. Although these tools serve their purpose by abstracting all the ‘complexity’ of deploying a smart contract, it may also be good to know what these tools do under the hood. As the tools automate many facets of the lifecycle of a smart contract, we will focus on just the compilation of a smart contract in todays post.

Intro Just a git commit to show this all is working as supposed.