File tree Expand file tree Collapse file tree 1 file changed +9
-9
lines changed
Expand file tree Collapse file tree 1 file changed +9
-9
lines changed Original file line number Diff line number Diff 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
9485Let'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
109109Let's look at this in two parts; gasPrice suggestion, and transaction sending.
You can’t perform that action at this time.
0 commit comments