Wallet.isEncryptedWallet

Hi, excuse me that i am asking here, however i cannot fix the issue for days. I try to make unlock wallet with keystore file, however devtool warn me

Uncaught TypeError: Wallet.isEncryptedWallet is not a function at UnlockWalletKeystore (ana.js:349) at HTMLButtonElement.onclick (index.html:200)

how can i fix this? probably my code is old and i should migrate to new version but i dont know how to do it. Excuse me again

function UnlockWalletKeystore() {
    var password = $("#keystorewalletpass").val();
    var buffer = fs.readFileSync(keyFile);
    var walletData = buffer.toString();
    $("#keystorebtn").html("Decrypting...");
    $("#keystorebtn").prop("disabled", true);

    if (password!='' && keyFile!='' && Wallet.isEncryptedWallet(walletData)){

        Wallet.fromEncryptedWallet(walletData, password).then(function(wallet) {
                console.log("Opened Address: " + wallet.address);
                wallet.provider = new ethers.providers.getDefaultProvider(false);
                myWallet = wallet;
                SuccessAccess();
                updateBalance();
                // UpdatePortfolio();
                $("#keystorebtn").html("Decrypting...");
        });
      } else {
        $("#keystorejsonerror").html('<i class="fas fa-exclamation-circle"></i> Invalid Keystore JSON File or Password')
        $("#keystorejsonerror").show();
        $("#keystorebtn").prop("disabled", false);
        $("#keystorebtn").html("Open");
      }
}

[ricmoo]

You are changing the contract address after you have already instantiated the Contract. Strings are immutable and passed by value, not by reference. So changing the string after passing it into somewhere else will have no effect.

You would need to make the Contract object re-assignable. This may lead to issues in other places though. I highly Recommend architecting the application to support changing networks, which would mean you have a function that setups up the world for a given network, on change: 1) tear down the old world and 2) rebuild the new one.

Otherwise you will always have lingering un-garbage-collects nuggets within your app resolving and possibly updating the UI after switching networks.

This is why I warn people of the absolute pain it is to support changing networks and to only do so if they absolutely need to. It is not simple… 😒

Does that help at all, though? 😃

[zemse]

@PlusBitPos Your myWallet doesn’t have a provider object attached to it, so after signing the transaction it doesn’t know which eth node backend it should send it to. So you need to connect it.

const provider = ethers.getDefaultProvider(); // for ethereum mainnet
myWallet = myWallet.connect(provider); // note that you are reasigning the myWallet js variable

You can also refer docs for wallet and providers.