You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I'm using "hardhat-deploy": "^0.11.44" and "@nomicfoundation/hardhat-toolbox-viem": "^2.0.0" libs
which are recommanded by hardhat official templates (with viem)
it automatically run deploy scripts when I run command "yarn hardhat node --hostname 0.0.0.0"
but calls to local hardhat network in golang seems reverted with no reason
It leads to hard to debug in local env
but it can call in online chains
To Reproduce
Steps to reproduce the behavior:
running 'yarn hardhat node --hostname 0.0.0.0' , it deploy contracts before local accounts shows up and didn't cost (may be the problem)
using generated abi in go to call methods but reverted with no reason (func sig error)
but it can successfully call in online chain but failed in hardhat node
versions
hardhat-deploy": "^0.11.44
@nomicfoundation/hardhat-toolbox-viem
"viem": "^1.19.11"
"hardhat": "^2.19.1"
go-ethereum
Additional context
Plz advise me some paths to debug with golang in local env using viem and hardhat-deploy
Check hardhat-deploy to fully support for Viem which recommands by hardhat official
The text was updated successfully, but these errors were encountered:
Describe the bug
I'm using "hardhat-deploy": "^0.11.44" and "@nomicfoundation/hardhat-toolbox-viem": "^2.0.0" libs
which are recommanded by hardhat official templates (with viem)
it automatically run deploy scripts when I run command "yarn hardhat node --hostname 0.0.0.0"
but calls to local hardhat network in golang seems reverted with no reason
It leads to hard to debug in local env
but it can call in online chains
To Reproduce
Steps to reproduce the behavior:
versions
Additional context
Plz advise me some paths to debug with golang in local env using viem and hardhat-deploy
Check hardhat-deploy to fully support for Viem which recommands by hardhat official
The text was updated successfully, but these errors were encountered: