0xPhaze

Does this work with `bytes32` and `bytes`? I am getting some weird results there. Edit: I guess these are always encoded as `string`.

Hm.. are you able to parse something like this?  I have to decode this into `string` and then parse the string to get the `bytes32`.

I've been running into the same issue. I'm still trying to verify on rinkeby. Pretty much happened exactly with the new recent update for me. Before it would at least...

Can't really tell what exactly is going wrong. However, this is how I've been handling it: ```js function useContract(contract) { const connector = usePriorityConnector(); const provider = usePriorityProvider(); contract =...

Maybe console2 could pick up these changes quicker than waiting for changes to console. And couldn't I just be required to explicitly cast to bytes32 in the case of ambiguity....

A somewhat cumbersome workaround is to compile it and to `vm.etch` the runtime code. You can also manually deploy it (with some args) and copy the code to etch (see...

Throwing in the idea of being able to tag certain broadcast transactions, and being able to reference them later via a cheat-code using something like shown in foundry-rs/forge-std#138. ```solidity function...

I'm not using any libraries with public functions. I'm working with already deployed contracts in my script, forking from mumbai. The `--verify` might have been misleading, because now, after running...

That did the trick for me, thank you very much. It was previously just not present in the config.

Interestingly it appeared again. I played around a bit again and removed the `--verify` and it then worked (but without verifying the contracts of course).