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 SiweMessage.verify function takes an optional second parameter of additional options, which includes a provider property to include an EthersJS Provider. Additionally, the SiweMessage.validate function takes an EthersJS Provider as a second property.
If a project wishes to supply those parameters, they must include EthersJS as a dependency in their project. In all other use cases, the implementing application doesn't need to know about EthersJS at all. (somewhat related to #151)
I believe the key piece of data the SIWE needs from the client is what RPC endpoint to call in order to make on-chain requests. Can those parameters be changed to be string inputs of an RPC URL rather than full Provider objects? Or allow the provider property to be sent as a string or a Provider, so implementing clients can choose?
The text was updated successfully, but these errors were encountered:
The
SiweMessage.verify
function takes an optional second parameter of additional options, which includes aprovider
property to include an EthersJS Provider. Additionally, theSiweMessage.validate
function takes an EthersJS Provider as a second property.If a project wishes to supply those parameters, they must include EthersJS as a dependency in their project. In all other use cases, the implementing application doesn't need to know about EthersJS at all. (somewhat related to #151)
I believe the key piece of data the SIWE needs from the client is what RPC endpoint to call in order to make on-chain requests. Can those parameters be changed to be string inputs of an RPC URL rather than full Provider objects? Or allow the
provider
property to be sent as astring
or aProvider
, so implementing clients can choose?The text was updated successfully, but these errors were encountered: