From c2c6c945244a51c79570692524ba34b8a3e20ab4 Mon Sep 17 00:00:00 2001 From: Georgios Konstantopoulos Date: Thu, 19 Aug 2021 10:08:59 +0300 Subject: [PATCH] chore: add explanation on `legacy` flag --- README.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/README.md b/README.md index e4e2e8af..6f45e8d5 100644 --- a/README.md +++ b/README.md @@ -30,6 +30,19 @@ In addition, it is recommended that you set the `ETHERSCAN_API_KEY` environment for [the abigen via Etherscan](https://github.com/gakonst/ethers-rs/blob/master/ethers/tests/major_contracts.rs) tests. You can get one [here](https://etherscan.io/apis). +### EVM-compatible chains support + +There are many chains live which are Ethereum JSON-RPC & EVM compatible, but do not yet have +support for [EIP-2718](https://eips.ethereum.org/EIPS/eip-2718) Typed Transactions. This means +that transactions submitted to them by default in ethers-rs will have invalid serialization. To +address that, you must use the `legacy` feature flag: + +```toml +[dependencies] + +ethers = { git = "https://github.com/gakonst/ethers-rs", features = ["legacy"] } +``` + ### Celo Support [Celo](http://celo.org/) support is turned on via the feature-flag `celo`: