-
Notifications
You must be signed in to change notification settings - Fork 25
BCFR-1330 #1161
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
Conversation
pkg/capabilities/triggers/testdata/fixtures/ondemand/schema.json
Outdated
Show resolved
Hide resolved
ilija42
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The exposed types look good, left some comments, some stuff needs to be in a separate PR and needs some polishing
pkg/types/relayer.go
Outdated
| Replay(ctx context.Context, fromBlock string, args map[string]any) error | ||
| } | ||
|
|
||
| type EVMClient interface { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| type EVMClient interface { | |
| // GethClient is the subset of go-ethereum client methods implemented by EVMService. | |
| type GethClient interface { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Regular GethClient doesn't guarantee support of any evm-family chain, should I clarify that these methods are any evm-family chain compatible then?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure that I follow, but I suppose it could be declared in package evm so then evm.GethClient from here? Would that help?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's just the naming GethClient is a little confusing, - yes the signatures are matching to the signatures of go-ethereum ethclient, but standart ethclient is not compatible with other than ethereum chains. evm client component guarantees compatibilty for the whole evm-family, but how the caller can be sure that GethClient will work with other than ethereum evm chains if we dont explicitly declare it?
Ticket
QueryTrackedLogs is coming in a separate PR
starknet ref: c7b7169940f7d9d355b4cb9fc4326e3ee7be2d21
core ref: fb5a9eb5264efc2f9f1ec99c397629c0d5f2f813