-
Notifications
You must be signed in to change notification settings - Fork 36
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
relayer: transaction sender impl #617
Conversation
012e6ab
to
9927e09
Compare
b5ea82f
to
07fe050
Compare
9927e09
to
30fb50a
Compare
30fb50a
to
1c800be
Compare
07fe050
to
121bf84
Compare
1c800be
to
a55bf5a
Compare
121bf84
to
6c1151a
Compare
a55bf5a
to
2d7c288
Compare
a24aec9
to
9d2be0d
Compare
2d7c288
to
fa2012d
Compare
7923e85
to
6dd8cb3
Compare
6dd8cb3
to
99d0dce
Compare
rs.Logger.Info().Msg("key generated") | ||
} | ||
|
||
// TODO deploy relayer's L2 smart account (if it is not exist) |
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 guess here relayer shout check and fails if smart account not exists.
All deployments are CLI tool responsibility
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.
We did not decide on CLI tool actually, just to make it a common code component :)
Anyway I would like to split smart account related logic from this PR
relayer: recompile l1/l2 ABI
20ce142
to
c4c6fb9
Compare
relayer: transaction sender impl
Implementation of relayer
TransactionSender
componentThis component is responsible for:
PR also contains L2 contract wrapper which provides an interface to interact with
L2BridgeMessenger
contract and some initial config for it (nil RPC endpoint, contract/account address, key). Current version only generates the key (if it is not exists). Other initialization stuff is going to be implemented in the following PRs