Skip to content

Commit 41d9fe4

Browse files
authored
Update docs/zkEVM/architecture/proving-system/exec-trace-and-zkevm.md
1 parent cfa58bf commit 41d9fe4

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/zkEVM/architecture/proving-system/exec-trace-and-zkevm.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ However, we don't know beforehand the exact EVM opcodes that will be executed.
44

55
Consequently, zkEVM operations to be executed are not known. This is so because these opcodes depend on the particular transactions included in L2 batches.
66

7-
Every transaction consists of multiple EVM Opcodes, and each EVM Opcode corresponds to multiple zkEVM Opcodes (i.e., The instructions that are in charge of what values are used to populate the execution trace).
7+
Every transaction consists of multiple EVM opcodes, and each EVM opcode corresponds to multiple zkEVM opcodes (i.e., The instructions that are in charge of what values are used to populate the execution trace).
88

99
This dependence is depicted in the figure below.
1010

0 commit comments

Comments
 (0)