From b9fe0991644bdb56febb4d85611135481e64cf53 Mon Sep 17 00:00:00 2001 From: Eva <1017762+eshon@users.noreply.github.com> Date: Tue, 18 Mar 2025 18:44:46 +0100 Subject: [PATCH 1/2] Update exchange-integration.md Fixing internal link to other section --- reference/exchanges/exchange-integration.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/reference/exchanges/exchange-integration.md b/reference/exchanges/exchange-integration.md index 9bac78f62..2908ad2c8 100644 --- a/reference/exchanges/exchange-integration.md +++ b/reference/exchanges/exchange-integration.md @@ -107,12 +107,12 @@ When `GasFeeCap`, `GasPremium` and `MaxFee` are set to `0`, Lotus will do the ga Some JavaScript libraries attempt to estimate the gas fees before sending the transaction to the Filecoin network. However, they sometimes underestimate, leading to transactions getting stuck in the mempool. If you are noticing your transactions getting stuck in the mempool after sending them to the network using a JavaScript library, try `GasFeeCap`, `GasPremium`, and `MaxFee` to `0`. -### Filecoin's EVM and Method number for sends +### Filecoin's EVM and Send method number -A summary of the Filecoin's EVM differences with Ethereum is available in the [FEVM - Difference with Ethereum section](/smart-contracts/filecoin-evm-runtime/difference-with-ethereum). +A summary of the Filecoin's EVM differences with Ethereum is available in the [FEVM - Difference with Ethereum section](../../smart-contracts/filecoin-evm-runtime/difference-with-ethereum). {% hint style="danger" %} -Note that when sending funds to a Filecoin EVM recipient address (`f410f` or `0x`), it is recommended to always use the `InvokeEVM` `method 3844450837` to prevent possible loss of funds in case the recipient is a smart contract. The `lotus send 0x` CLI method always defaults to this method number. +Note that when sending funds to a Filecoin EVM recipient address (f410f or 0x), it is recommended to always use the **InvokeEVM** **method 3844450837** to prevent possible loss of funds in case the recipient is a smart contract. The `lotus send 0x` CLI method always defaults to this method number. {% endhint %} From c2ff9753ddbdd4bf2d1b2ad7a8581af46e5d0c59 Mon Sep 17 00:00:00 2001 From: Eva <1017762+eshon@users.noreply.github.com> Date: Tue, 18 Mar 2025 18:46:20 +0100 Subject: [PATCH 2/2] Update exchange-integration.md fixing link again --- reference/exchanges/exchange-integration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/reference/exchanges/exchange-integration.md b/reference/exchanges/exchange-integration.md index 2908ad2c8..c4e6d9831 100644 --- a/reference/exchanges/exchange-integration.md +++ b/reference/exchanges/exchange-integration.md @@ -109,7 +109,7 @@ Some JavaScript libraries attempt to estimate the gas fees before sending the tr ### Filecoin's EVM and Send method number -A summary of the Filecoin's EVM differences with Ethereum is available in the [FEVM - Difference with Ethereum section](../../smart-contracts/filecoin-evm-runtime/difference-with-ethereum). +A summary of the Filecoin's EVM differences with Ethereum is available in the [FEVM - Difference with Ethereum section](../../../smart-contracts/filecoin-evm-runtime/difference-with-ethereum). {% hint style="danger" %} Note that when sending funds to a Filecoin EVM recipient address (f410f or 0x), it is recommended to always use the **InvokeEVM** **method 3844450837** to prevent possible loss of funds in case the recipient is a smart contract. The `lotus send 0x` CLI method always defaults to this method number.