Matt Solomon

Can you provide another RPC URL? This one does not seem to work. Additionally, the deployer account `0x05f32B3cC3888453ff71B01135B34FF8e41263F2` has no balance, but it says deployment funds were sent ``` $...

The README command is correct, but some nodes require EIP-155 which means the transaction must be signed over chain ID for replay protection. The readme's transaction is intentionally not signed...

You can either run your own node for that chain that does not enforce EIP-155 (AllowUnprotectedTxs flag in geth), or someone with the private key (e.g. me for multicall3) needs...

There is a presigned transaction in the README so users can deploy on EVM-compatible chains without opening an issue. I don't want to deploy using that deployer (or similar ones)...

Yes, there are multiple ways to do this, such as `aggregate3` method with `allowFailure` set to false. Please see the readme and Multicall3 contract itself for more info

`not approved` sounds like an error with your specific calls, since multicalls do work with any method type. I'm not familiar with the `collect` method, but if you need more...

Yes you can interact it with it just like you would with any other contract. If you have specific questions about web3.py I'd suggest opening issues in the web3.py repo...

Even when specifying an amount of gas to forward, you'd still be susceptible to DoS attacks because of return data bombs that can still forcibly use the rest of your...

The current balance of the deployer account appears to be too low, which looks like is because chain has a very high gas price: > You do not have enough...

Thanks! Can you verify the code first? I was unable to verify it, and the bytecode is much shorter than the bytecode on mainnet, and blockscout usually can automatically verify...