From f50aedf621fd3bb2f28abd6e804dc238eefc834f Mon Sep 17 00:00:00 2001 From: qsysvcore Date: Sat, 28 Mar 2026 15:50:31 +0300 Subject: [PATCH] docs: fix broken markdown link in best-practices.mdx --- how-abstract-works/evm-differences/best-practices.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/how-abstract-works/evm-differences/best-practices.mdx b/how-abstract-works/evm-differences/best-practices.mdx index 7fc8218..0abc51d 100644 --- a/how-abstract-works/evm-differences/best-practices.mdx +++ b/how-abstract-works/evm-differences/best-practices.mdx @@ -41,7 +41,7 @@ Some additional changes may be required in your contract. [Learn more in this se [EIP-712](https://eips.ethereum.org/EIPS/eip-712) transactions have a `gasPerPubdataByte` field that can be set to control the amount of gas that is charged for each byte of data sent to L1 -(see [transaction lifecycle](/how-abstract-works/architecture/transaction-lifecycle)). [Learn more ↗](https://docs.zksync.io/zksync-protocol/rollup/fee-model/how-we-charge-for-pubdata. +(see [transaction lifecycle](/how-abstract-works/architecture/transaction-lifecycle)). [Learn more ↗](https://docs.zksync.io/zksync-protocol/rollup/fee-model/how-we-charge-for-pubdata). When calculating how much gas is remaining using `gasleft()`, consider that the `gasPerPubdataByte` also needs to be accounted for.