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

Can we support different JSON-RPC request and response types in the provider? #438

Closed
2 tasks done
Tracked by #373
Wodann opened this issue May 7, 2024 · 0 comments · Fixed by #483 or #488
Closed
2 tasks done
Tracked by #373

Can we support different JSON-RPC request and response types in the provider? #438

Wodann opened this issue May 7, 2024 · 0 comments · Fixed by #483 or #488
Assignees
@Wodann

Comments

@Wodann
Copy link
Collaborator

Wodann commented May 7, 2024 •
edited

  • How can we have chain-specific JSON-RPC requests?
  • How can we have chain-specific response types (e.g. a different transaction or block type)?
@Wodann Wodann mentioned this issue May 7, 2024
Open
7 tasks
@Wodann Wodann changed the title How can we support different JSON-RPC request and response types in the provider? Can we support different JSON-RPC request and response types in the provider? May 7, 2024
@Wodann Wodann self-assigned this May 7, 2024
This was linked to pull requests Jun 4, 2024
refactor: use generic trait bound for RpcClient #483
Merged
refactor: rename transaction types to avoid collisions #488
Merged
@Wodann Wodann reopened this Jun 5, 2024
@Wodann Wodann closed this as completed Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Wodann Wodann

Labels
None yet
Projects
EDR
Status: Done
Milestone
No milestone
1 participant
@Wodann