zerosnacks

Me too! Some ways Weiroll is being used currently: - Rapid development of yield farming automation (harvest, compound, rebalancing, etc..) without the deployment of individual strategy contracts - Programmatic complex...

I think it is a bit verbose and for most use cases the level of detail seems unnecessary @mablr would you mind expanding on where you use the public keys?...

Hey @mablr, I see - thanks for the pointer! To my understanding @mattsse refers to `checking if this is verbose or not` to indicate we should only display the public...

Hi @jgresham I'm very excited for EIP-7907! Feel free to open a draft PR. Regarding the max sizes, I can imagine we will default to using the new contract size...

Hi @knelsondev unfortunately these changes do not resolve the compilation warnings; please see the instructions in the ticket on how to iteratively fix them

Hi @knelsondev, ah yes - in the latest nightly we have enabled the running of `forge lint` by default. You can disable this by setting: ``` [lint] lint_on_build = false...

Continuing on this to find out what next steps are. As discussed, going to run a nightly release against: https://github.com/foundry-rs/foundry/compare/master...grandizzy/attestation-url This should create an *.attestation.txt file we can then make...

Perfect, running here: https://github.com/foundry-rs/foundry/actions/runs/16023228220

cc @yash-atreya Similar to https://github.com/foundry-rs/foundry/pull/9021 I think

Able to reproduce, state looks like this: Where `sender` is `0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266` to `0x9276449EaC5b4f7Bc17cFC6700f7BeeB86F9bCd0` When reloading the state it attempts to send with nonce `784` instead of `785` ```json { "block":{...