LumeWeb
/
ethers-rs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

chore: add explanation on `legacy` flag

This commit is contained in:
Georgios Konstantopoulos 2021-08-19 10:08:59 +03:00 committed by GitHub
parent 42aeeedcce
commit c2c6c94524
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 13 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
README.md
View File

@ -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`: