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
The idea is that whenever a new Ethers provider or signer is accepted, the SDK starts by checking it's type. If it's an ethers provider or signer, the SDK should do nothing. If it's a Viem provider or signer, the Viem adaptor code (linked here) should be run first so that the correct ethers-compatible provider or signer can be passed into the Lit JS SDK function that needs it.
Motivation
This functionality will make the JS SDK "Viem compatible" and makes it really easy to use the Lit JS SDK on any dApp that is using Viem.
The text was updated successfully, but these errors were encountered:
Overview
The idea is that whenever a new Ethers provider or signer is accepted, the SDK starts by checking it's type. If it's an ethers provider or signer, the SDK should do nothing. If it's a Viem provider or signer, the Viem adaptor code (linked here) should be run first so that the correct ethers-compatible provider or signer can be passed into the Lit JS SDK function that needs it.
Motivation
This functionality will make the JS SDK "Viem compatible" and makes it really easy to use the Lit JS SDK on any dApp that is using Viem.
The text was updated successfully, but these errors were encountered: