Invalid Mnemonic When Wallet is Constructed From Self

[jettblu]

Ethers Version

5.6

Search Terms

No response

Describe the Problem

Hello! When a wallet is constructed with a private key, 'connect' throws an error.

This is likely due to hasMnemonic returning true even though the mnemonic is not explicitly set when the wallet is constructed from a private key (appears to default to "not set"). My workaround changes the connect method body to:

return new WalletEthers(this.privateKey, provider);

This should work, as the wallet private key is always available (we only need to validate it). However, there may be some properties from the wallet object that you want to retain when connecting to a provider.

If you have any questions, please let me know.

Code Snippet

let provider = new StaticJsonRpcProvider("https://rpc.ankr.com/eth");
let privateKey = "0x3141592653589793238462643383279502884197169399375105820974944592"
let walletNew = new WalletEthers(privateKey);
walletNew.connect(provider);

Contract ABI

No response

Errors

Error: invalid mnemonic

Environment

node.js (v12 or newer)

Environment (Other)

No response

[zemse]

Using .connect(provider) on a wallet without a provider should work (I just rechecked). You try that on playground. Maybe the issue is coming from somewhere else, are you extending ethers.Wallet class?

[jettblu]

Using .connect(provider) on a wallet without a provider should work (I just rechecked). You try that on playground. Maybe the issue is coming from somewhere else, are you extending ethers.Wallet class?

Gotcha', but the issue is with using .connect(provider) on a wallet constructed from a private key.

[ricmoo]

I think the error may be somewhere else in your code? I just tried this example and it works fine.

Keep in mind your code above won't do anything; connect does not change the current provider, as a Signer is immutable. It returns a new instance of the Wallet, so you likely want wallet = new Wallet(privateKey).connect(provider);.