Build and adopt an Ubiquitous Language for Kakarot

[Eikix]

Hey all,

After discussion on the Kakarot Telegram group, we noticed that there is still doubt about the terms we use.

As an example, when contributors talk about an EVM contract deployed through Kakarot, they sometimes use the word storage account, sometimes evm contract, sometimes contract account.

It is essential for the project's clarity to have a common language in order to describe our core concepts.

In this effort, we shall discuss unique terms to describe Kakarot specific objects.

The discussion will result in refactor of the code to properly name every concept. Moreover, people will use these terms in everyday conversation with product owners, stakeholders and other devs.

We will consequently save a glossary of the resulting agreed upon terms.

[Eikix]

For now, concepts I can think of, that we need to address and "name" officially:

• an EVM smart contract, deployed through Kakarot -> a starknet smart contract, holding in storage the whole EVM bytecode of our EVM smart contract
• an EVM smart contract, deployed on an EVM chain -> an EVM smart contract, in an EVM environment
• arbitrary EVM bytecode
• a normal starknet smart contract
• memory -> the stack machine - memory type of memory: volatile, 8-bit word length, addressed by offset.
• stack -> stack machine - memory type of stack: volatile, 32-bit word length, FIFO
• calling a Kakarot EVM contract -> executing bytecode stored in a kakarot-deployed starknet contract
• initialising a kakarot EVM contract -> running the constructor code
• accessing a kakarot EVM contract storage (read/write) -> factually reading/writing a starknet storage var, but essentially as if it were an EVM storage var