Closed tab00 closed 1 year ago
Hi @tab00 ,
thanks for reporting this. Do you run your own node or do you use forno?
I'm using RPC https://alfajores-forno.celo-testnet.org
I can reproduce this:
Here's the whole snippet:
// const provider = new ethers.JsonRpcProvider("https://forno.celo.org");
const provider = new ethers.JsonRpcProvider("https://alfajores-forno.celo-testnet.org");
// const provider = new ethers.JsonRpcProvider("https://baklava-forno.celo-testnet.org");
// const provider = new ethers.JsonRpcProvider("https://forno.cannoli.celo-testnet.org");
// const provider = new ethers.JsonRpcProvider("http://localhost:8545");
const feeData = await provider.getFeeData()
console.log(feeData)
Do we just need to update the blockchain nodes, or is there a specific reason why alfajores and baklava fail? Why does alfajores have the problem but not mainnet?
This problem has been fixed in https://github.com/celo-org/celo-blockchain/commit/6043494d72d000e10cb6105a35f650d5b7de12e6 and will be resolved on alfajores as soon as the node is updated.
Expected Behavior
JavaScript running ethers completes without the error.
Actual Behavior
Script terminates with error message:
This doesn't happen on other blockchains.
Steps to reproduce the behavior
Run a script that has this JavaScript code:
Backtrace
System Information
ethers 6.7.0
Chain/Network:
Alfajores