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.

Sign up for GitHub

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

Jump to bottom

Abstract client spec to be compatible with different clients #227

Open
zsluedem opened this issue Oct 15, 2023 · 1 comment
Open

Abstract client spec to be compatible with different clients #227

zsluedem opened this issue Oct 15, 2023 · 1 comment
Labels
A-core Area: Related to core components high priority This should be done soon T-enhancement Type: Enhancement to existing feature

Comments

@zsluedem
Copy link
Collaborator

Currently, only geth could support all the features normally for Silius bundler.

  1. Erigon would have some problems on estimate gas Seeing "Unknown error when simulating validation on entry point" during eth_estimateUserOperationGas #225
  2. Nethermind doesn't support debug_tracecall with js tracer.
  3. Besu and Reth haven't tested yet.

We should have a compatible layer which could support all the execution clients.
@Vid201
Copy link
Member

Vid201 commented Oct 15, 2023

Currently, only geth could support all the features normally for Silius bundler.

  1. Erigon would have some problems on estimate gas Seeing "Unknown error when simulating validation on entry point" during eth_estimateUserOperationGas #225
  2. Nethermind doesn't support debug_tracecall with js tracer.
  3. Besu and Reth haven't tested yet.

We should have a compatible layer which could support all the execution clients.

That's an interesting idea. We can then display in logs for example that unsafe mode is used for clients that doesn't support debug trace calls.

@Vid201 Vid201 mentioned this issue Oct 16, 2023
Closed
@Vid201 Vid201 added T-enhancement Type: Enhancement to existing feature high priority This should be done soon A-core Area: Related to core components labels Dec 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-core Area: Related to core components high priority This should be done soon T-enhancement Type: Enhancement to existing feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zsluedem @Vid201