InnovationWeb3
commented
3 weeks ago Hey, sorry for the delay. We’ve been really busy lately, but we’ll be back with new projects and updates on the current one.
Have you solved your issue yet? If not, please ensure that Infura_API_KEY is correctly set. At the top of the bot.js file, add the following line
console.log('Infura API Key:', process.env.Infura_API_KEY)
Then relaunch the bot. If the log shows something unexpected, that may not be the issue.
You can also try using this format instead
const provider = new ethers.providers.WebSocketProvider(wss://eth-mainnet.g.alchemy.com/v2/${process.env.Alchemy_API_KEY})
Additionally, ensure that the Node.js version you’re using is compatible with your dependencies. You might want to switch to an older version; we plan to update this project with the newest Node version in October.
Let us know if this solves the issue.
dorohov7
An error occurs when launching the bot: “C:\Arbitrage-Bot-main>node bot.js C:\Arbitrage-Bot-main\helpers\initialization.js:26 provider = new hre.ethers.WebSocketProvider( (C:\Arbitrage-Bot-main\helpers\initialization.js:26:29)
at Module._compile (node:internal/modules/cjs/loader:1546:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1691:10)
at Module.load (node:internal/modules/cjs/loader:1317:32)
at Module._load (node:internal/modules/cjs/loader:1127:12)
at TracingChannel.traceSync (node:diagnostics_channel:315:14)
at wrapModuleLoad (node:internal/modules/cjs/loader:217:24)
at Module.require (node:internal/modules/cjs/loader:1339:12)
at require (node:internal/modules/helpers:135:16)
at Object. (C:\Arbitrage-Bot-main\bot.js:8:71)”
Node.js v22.9.0
wss://eth-mainnet.g.alchemy.com/v2/${process.env.Infura_API_KEY}); ^ TypeError: Cannot read properties of undefined (reading 'WebSocketProvider') at Object.