You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/zkEVM/architecture/user-fees.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -214,7 +214,7 @@ $$
214
214
$$
215
215
216
216
217
-
### Numerical example: $\texttt{L2MinGasPrice}$
217
+
### Numerical example: L2MinGasPrice
218
218
219
219
In the figure below, we observe that when the user queries the suggested gas price through the RPC, the network responds with the current suggested gas price computed as:
220
220
@@ -389,7 +389,7 @@ Observe that users must trust the sequencer in this schema.
389
389
390
390
391
391
392
-
## Introducing $\texttt{BreakEvenGasPrice}$
392
+
## Introducing BreakEvenGasPrice
393
393
394
394
The aim here is for the Polygon zkEVM network to avoid accepting transactions that result in financial losses.
395
395
@@ -495,7 +495,7 @@ Observe that we still need to introduce gas price prioritization, which will be
Recall the example proposed before, where the $\texttt{GasPriceSuggested}$ provided by RPC was $2.85$ gwei per gas, but the user ended up setting $\texttt{GasPriceSigned}$ to $3.3$.
0 commit comments