Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Is there a way to connect a signer to another network (provider)?
See original GitHub issueIn ethers.js is it possible to connect a signer from one network to another network? So metamask is connected to mainnet - and you use an rpc provider connected to another sidechain but using the same private keys.
The use case is when using the gas station network (gsn: https://opengsn.org), you may have a side chain that is connected to a different network using gsn, but using the same account/private key.
When I use the .connect method on a signer that is already connected to another network I get this error: Error: cannot alter JSON-RPC Signer connection (operation="connect", code=UNSUPPORTED_OPERATION, version=providers/5.0.10)
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yeah, I think it would work with metamask. I tested it with a random wallet, not with metamask. But, I can confirm later. Keep in mind that this GsnSigner only supports GSN v1.0, not the latest v2.0.
The GsnSigner was implemented to take another signer as input in the constructor and overrides the sendTransaction() method to send the signed transaction to the GSN network.
Cool cool.
Yeah, gsn works fine since it just uses signed EIP-191 payloads with the personal message profile (I think?) which MetaMask does support.
@yuetloo can comment more on that though. 😃