John Kane
John Kane
I am reopening this issue. My understanding is that our re-calibration of checks and timeouts resolved the `all the transactions of its network interaction 1 were dropped.` and `nonce not...
Looking at `vite`, they seem to have made the call not to support `#` in file paths: https://github.com/vitejs/vite/issues/13123
That is interesting. I don't think we would change passing args as an array to say an object with named properties matching the Solidity function parameter names. However we may...
A helper function on top of the Module API would work.
We will do this when we migrate to the Hardhat repo.
We have started taking a look at this and will update here as we make progress.
> Same issues :( Hey @csurbier, could you give us more details of the chain you are deploying to, what you see in terms of gas fees and what you...
> Hi, > > Try again same smart contracts, same ignition command to deploy but on SEPOLIA network. No gas fees issues, deployed with few gas fees: https://sepolia.etherscan.io/address/0x169A3AF28ed1C191E273de870003493e6102f138 > >...
Ignition takes responsibility for calculating gas fees, the logic was developed with a focus on L1, we are seeing issues when targeted against Polygon as it uses different logic to...
Perhaps an approach here is to enhance the return result from `core`'s `status` function: ``` export interface GenericContractInfo extends DeployedContract { sourceName: string; abi: Abi; deployedBlockNumber: number //