Using the sepolia testnet leads to error

[nnseva]

Hi! I am a novice in smart contracts and Ethereum, so I have started with the Hello World application here. They recommend using sepolia instead of goerli test net, and I followed this suggestion.

Unfortunately, it led me to a problem, when I tried to request the smart contract, as described there (similar, but different link).

Error: unsupported network (argument="network", value={"name":"sepolia","chainId":11155111}, code=INVALID_ARGUMENT, version=providers/5.7.2)
    at Logger.makeError (/disk0/home/seva/OGOO/node_modules/@ethersproject/logger/src.ts/index.ts:269:28)
    at Logger.throwError (/disk0/home/seva/OGOO/node_modules/@ethersproject/logger/src.ts/index.ts:281:20)
    at Logger.throwArgumentError (/disk0/home/seva/OGOO/node_modules/@ethersproject/logger/src.ts/index.ts:285:21)
    at AlchemyProvider.getUrl (/disk0/home/seva/OGOO/node_modules/@ethersproject/providers/src.ts/alchemy-provider.ts:83:23)
    at AlchemyProvider.UrlJsonRpcProvider [as constructor] (/disk0/home/seva/OGOO/node_modules/@ethersproject/providers/src.ts/url-json-rpc-provider.ts:60:71)
    at new AlchemyProvider (/disk0/home/seva/OGOO/node_modules/@ethersproject/providers/lib/alchemy-provider.js:51:42)
    at Object.<anonymous> (/disk0/home/seva/OGOO/scripts/interact.js:15:25)
    at Module._compile (node:internal/modules/cjs/loader:1241:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1295:10)
    at Module.load (node:internal/modules/cjs/loader:1091:32)

I have found that the AlchemyProvider.getUrl function does not know anything about sepolia test net although other code contains many references to this name.

Searching in the issues list, I've found this yet open ticket where the sepolia support is planned to v6. I am using ethers@6.8.1 and the problem still exists.

Investigating the stack, I've found that small change in the alchemy-provider.ts file makes things work. It's only necessary to add something like

            case "sepolia":
                host = "eth-sepolia.g.alchemy.com/v2/";
                break;

to the switch in the AlchemyProvider.getUrl method. Unfortunately, it's hard to find where is this code file from.

Please fix this problem, or just explain how to workaround it.

[ricmoo]

Your above error indicates you are using v5.7.2 of ethers. Sepolia is supported in v6 though; make sure when you install ethers you don’t have the wrong version indicated in your package.json or package-lock.json.

You can always use console.log(ethers.version) to check too. :)

[nnseva]

Thanx, but this report looks like the version 6.8.1 is installed, isn't it?

seva@SEVA-MOBILE:~/OGOO$ npm show ethers

ethers@6.8.1 | MIT | deps: 7 | versions: 306
A complete and compact Ethereum library, for dapps, wallets and any other tools.
https://ethers.org

keywords: ethereum, ethers, ethersjs

dist
.tarball: https://registry.npmjs.org/ethers/-/ethers-6.8.1.tgz
.shasum: ee2a1a39b5f62a13678f90ccd879175391d0a2b4
.integrity: sha512-iEKm6zox5h1lDn6scuRWdIdFJUCGg3+/aQWu0F4K0GVyEZiktFkqrJbRjTn1FlYEPz7RKA707D6g5Kdk6j7Ljg==
.unpackedSize: 12.1 MB

dependencies:
@adraffy/ens-normalize: 1.10.0 @noble/hashes: 1.3.2           aes-js: 4.0.0-beta.5           ws: 8.5.0                      
@noble/curves: 1.2.0           @types/node: 18.15.13          tslib: 2.4.0                   

maintainers:
- ricmoo <me@ricmoo.com>

dist-tags:
latest: 6.8.1      legacy-v4: 4.0.49  legacy-v5: 5.7.2   

published 2 days ago by ricmoo <me@ricmoo.com>

[ricmoo]

I think npm show just queries the remote server. You can verify locally by using npm list or cat node_modules/ethers/package.json.

I’m just going by your error, which indicates 5.7.2; ethers bakes the version string into all errors to help debug these sorts of issues. :)

[nnseva]

Some other packages require lesser versions of the ethers package. I have got an error when tried to install all necessary packages:

seva@SEVA-MOBILE:~/OGOO$ npm install hardhat@latest @nomiclabs/hardhat-ethers@latest ethers@latest
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: ogoo@0.0.1
npm ERR! Found: ethers@6.8.1
npm ERR! node_modules/ethers
npm ERR!   ethers@"6.8.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer ethers@"^5.0.0" from @nomiclabs/hardhat-ethers@2.2.3
npm ERR! node_modules/@nomiclabs/hardhat-ethers
npm ERR!   @nomiclabs/hardhat-ethers@"2.2.3" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /disk0/home/seva/.npm/_logs/2023-11-03T14_16_06_687Z-eresolve-report.txt

Thank you for explanation. Sorry for disturb.

[ricmoo]

Modern hardhat works fine with v6; you may have to delete the package-lock.json entirely and let npm rebuild it?

[nnseva]

Actually, I have noticed that the tutorial which I red, refers to the @nomiclabs where packages are using deprecated versions of ethers package.

To make a new version available, the @nomicfoundation should be used instead. This dependency list works fine:

  "dependencies": {
    "@nomicfoundation/hardhat-ethers": "^3.0.4",
    "dotenv": "^16.3.1",
    "ethers": "^6.8.1",
    "hardhat": "^2.19.0"
  }

Also some calls to the ethers in the tutorial appear to be incompatible (particularly, ethers.providers.AlchemyProvider is not working) and should be rewritten in a new style.

It also looks like contract compiled and uploaded by the old version is not compatible with a new library version (checking it right now), and should be reuploaded...

UPD: I am not right, the contract is compatible! It was my mistake.