teddy

Thanks for reporting this. This package is indeed coupled to ethers v5 and supporting ethers v6 would require some refactoring and a major version change. We can get to it...

> Does anyone have advice for getting this to work? Any workarounds? if you want to take care of this, we could review & merge it. While you could just...

> do you have a branch open where you started these changes? I'd be open to checking it out and attempting to continue chipping away at this. All the changes...

> I guess this repo assumes that all contracts are using interfaces? That is indeed the case! We are pushing to have the entirety of a contract's ABI extracted into...

hello @SamWilsn , I have some editorial questions: - What should I do about the extra sections? the EIP Walidator [reports on them](https://github.com/ethereum/ERCs/actions/runs/14517629842/job/40730439882?pr=1002) but I believe they make a more...

hi @SamWilsn ! Implemented all feedback that I could from eip walidator, but there are a few things I couldn't get around: - [ ] I got myself into a...

update: since it's not required to link to CAIPs, I removed links to CAIP-350, in order to minimize the amount of warnings. I'll link to CAIP-350 once we have a...

> Putting both in the same PR, but generally speaking we prefer an acyclic graph of dependencies. If you feel strongly about it, I'll make an exception. I do feel...

this is related to #6908

update: I went for the 'run the entire CI inside a container' option, which proved simple enough if we maintain a fork of the docker image, see https://github.com/0xteddybear/eth-security-toolbox-ci/pull/1 TODO -...