You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Although viem is the "new kid in town", it provides a very pleasand and efficient API, it is astonishingly well-documented (see it yourselves at viem.sh), and is becoming popular extremely fast (look at the library trends here: https://npmtrends.com/ethers-vs-viem-vs-web3).
@farreldarian perhaps also the strategy of a custom transport implementing EIP-1193 could be a good less-heavy alternative. What do you think? (see #651)
@farreldarian perhaps also the strategy of a custom transport implementing EIP-1193 could be a good less-heavy alternative. What do you think? (see #651)
I designed it to be compatible with any client, allowing you to initialize it with any type of transport. (ref)
Although viem is the "new kid in town", it provides a very pleasand and efficient API, it is astonishingly well-documented (see it yourselves at viem.sh), and is becoming popular extremely fast (look at the library trends here: https://npmtrends.com/ethers-vs-viem-vs-web3).
Please consider adding an adapter supporting it!
Extras
Related stackexchange thread by other people: https://ethereum.stackexchange.com/questions/155920/viemadapter-for-safe-global-protocol-kit?newreg=4a47bdd49aa04caf8c92ae0eec448c46
The text was updated successfully, but these errors were encountered: