Skip to content

Commit 18e1a30

Browse files
Merge pull request 0xPolygon#244 from 0xPolygon/EmpieichO-patch-1
Update user-fees.md - fix sidebar titles
2 parents 052d779 + e16a8be commit 18e1a30

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/zkEVM/architecture/user-fees.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -214,7 +214,7 @@ $$
214214
$$
215215

216216

217-
### Numerical example: $\texttt{L2MinGasPrice}$
217+
### Numerical example: L2MinGasPrice
218218

219219
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:
220220

@@ -389,7 +389,7 @@ Observe that users must trust the sequencer in this schema.
389389

390390

391391

392-
## Introducing $\texttt{BreakEvenGasPrice}$
392+
## Introducing BreakEvenGasPrice
393393

394394
The aim here is for the Polygon zkEVM network to avoid accepting transactions that result in financial losses.
395395

@@ -495,7 +495,7 @@ Observe that we still need to introduce gas price prioritization, which will be
495495

496496

497497

498-
### Numerical example: Computing $\texttt{BreakEvenGasPrice}$
498+
### Numerical example: Computing BreakEvenGasPrice
499499

500500
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$.
501501

@@ -587,7 +587,7 @@ $$
587587

588588

589589

590-
## $\texttt{EffectiveGasPrice}$: Introducing Priority
590+
## EffectiveGasPrice: Introducing Priority
591591

592592
Prioritization of transactions in Ethereum is determined by $\texttt{GasPriceSigned}$ and transactions signed at a higher price are given priority.
593593

0 commit comments

Comments
 (0)