Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update readme with fork rationale #334

Open
cryptix opened this issue Jun 26, 2024 · 1 comment
Open

Update readme with fork rationale #334

cryptix opened this issue Jun 26, 2024 · 1 comment

Comments

@cryptix
Copy link

cryptix commented Jun 26, 2024

Hi,

Thanks a lot for this! I found this repo via the transaction type not supported issue on upstream.

As far as I can tell the main reason for the fork is/was L2 support but which networks exactly are in/out of scope and whether this fork also still works to interact with L1 is really hard to tell from the outside since the README is still the upstream one, I believe?

Maybe this information is somewhere else. I haven't been able to find it if so.

@bbenzikry
Copy link

We tried the latest passing master and it didn't seem to work well on L2s we work with.
We ended up using our up to date geth fork and just handled opstack and others ourselves ( mostly for ethclient use though )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants