Skip to content
This repository has been archived by the owner on Jan 9, 2025. It is now read-only.

docs/Deployment Process #409

Merged
merged 4 commits into from
Jan 10, 2023
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
small docs format change
  • Loading branch information
TotalPizza committed Jan 6, 2023
commit 8a7fd5c129d9b827826b4104653845a5fd82166a
6 changes: 2 additions & 4 deletions docs/general/kakarot_components.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,9 +50,7 @@ With the above information in mind the Kakarot EVM can be deployed and configure

This generates a class hash which will be used by the core Kakarot contract to deploy *Contract Accounts*.

2. Deploy Kakarot (core)

The Kakarot core contract requires the following constructor arguments:
2. Deploy Kakarot (core), with the following constructor arguments:
- StarkNet address of the owner/admin account that controls the Kakarot core contract.
- Address of the ETH token contract (Which is also used as ether within the Kakarot EVM)
- *Contract Account* class hash.
Expand All @@ -61,4 +59,4 @@ The Kakarot core contract requires the following constructor arguments:

4. Deploy Blockhash Registry

5. Store the addresses of the account and blockhash registry contracts in kakarot core using `set_account_registry` and `set_blockhash_registry` respectively. This is required for Kakarot to access the functionality of the registries.
5. Store the addresses of the account and blockhash registry contracts in Kakarot core using `set_account_registry` and `set_blockhash_registry` respectively. This is required for Kakarot to access the functionality of the registries.