Ethers v6 Migration Guide
Support for ethers v6 and migration guides for moving code from ethers v5 to v6
The @0xsequence package v2.0 now requires at a minimum the Ethers version ethers@6.13.0
.
If you are unable to upgrade to ethers v6, then you can use v1.10.5 of @0xsequence or 3.0.0 of @0xsequence/kit.
If you’ve been developing with ethers@^5.0.0
in the past, outlined below are the common ways using Ethers with Sequence will change for you:
Static and Default RPC Provider
To use ethers to connect and make RPC calls to a blockchain node in order to query information, doing so in a static or default way both have differences:
Big Number Support
If you’re using big numbers to generate randomly spaced token ID’s, nonces, or some other application of large string based numbers, ethers now supports built-in ES2020 BigInt offered by modern JavaScript environments.
Removal of Ethers Utilities
Using Ethers you will notice there is no longer a ethers.utils
path. Therefore, all paths should be updated without the utils
:
Utility Hash Value Packing
If you’re using ethers utilities to perform signature creation then using ecrecover
on-chain, signature creation is now slightly different:
For complete information on the differences of Ethers v5
to v6
you can read more here in the official docs.
Was this page helpful?