Skip to content

Commit 4bd2469

Browse files
committed
update zkEVM - minor edits
1 parent 5e8c3d2 commit 4bd2469

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

docs/zkEVM/architecture/user-fees.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -80,15 +80,6 @@ Their corresponding pertinent questions are:
8080
- How do L2 solutions address and reconcile any discrepancies between the L1 gas schema and the real resource utilization on L2?
8181

8282

83-
### Time-related variations
84-
85-
So, how can the fact that the L1 $\texttt{gasPrice}$ varies with time be taken into account?
86-
87-
In order to obtain L1 gas prices, we can poll for it every 5 seconds. As shown in the timeline below, gas prices vary with time.
88-
89-
![Figure: Gas price timeline](../../img/zkEVM/gas-timeline-001.png)
90-
91-
9283
## Gas price suggester
9384

9485
Let's take a quick view of the initial phase of the process, which involves the RPC component of zkEVM.
@@ -104,6 +95,15 @@ See the the picture below for an overview of the pre-execution process.
10495
![Figure: RPC tx pre-execution](../../img/zkEVM/rpc-tx-preexec.png)
10596

10697

98+
### Time-related variations
99+
100+
So, how can the fact that the L1 $\texttt{gasPrice}$ varies with time be taken into account?
101+
102+
In order to obtain L1 gas prices, we can poll for it every 5 seconds. As shown in the timeline below, gas prices vary with time.
103+
104+
![Figure: Gas price timeline](../../img/zkEVM/gas-timeline-001.png)
105+
106+
107107
### Naïve approach
108108

109109
Let's look at this in two parts; gasPrice suggestion, and transaction sending.

0 commit comments

Comments
 (0)