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

relayer: transaction sender impl #617

Merged
merged 1 commit into from
Mar 31, 2025
Merged

relayer: transaction sender impl #617

merged 1 commit into from
Mar 31, 2025

Conversation

oclaw
Copy link
Contributor

@oclaw oclaw commented Mar 20, 2025

Implementation of relayer TransactionSender component

This component is responsible for:

  • Fetching event from L2 storage
  • Ordered forwarding of the events to the L2
  • Dropping events from L2 storage

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

@oclaw oclaw force-pushed the feature/relayer-tx-sender branch from 012e6ab to 9927e09 Compare March 21, 2025 15:02
@oclaw oclaw force-pushed the feature/relayer-fin-ensurer branch 2 times, most recently from b5ea82f to 07fe050 Compare March 21, 2025 17:41
@oclaw oclaw force-pushed the feature/relayer-tx-sender branch from 9927e09 to 30fb50a Compare March 21, 2025 17:43
@oclaw oclaw force-pushed the feature/relayer-tx-sender branch from 30fb50a to 1c800be Compare March 21, 2025 17:47
@oclaw oclaw force-pushed the feature/relayer-fin-ensurer branch from 07fe050 to 121bf84 Compare March 21, 2025 17:53
@oclaw oclaw force-pushed the feature/relayer-tx-sender branch from 1c800be to a55bf5a Compare March 21, 2025 17:54
@oclaw oclaw force-pushed the feature/relayer-fin-ensurer branch from 121bf84 to 6c1151a Compare March 21, 2025 18:02
@oclaw oclaw force-pushed the feature/relayer-tx-sender branch from a55bf5a to 2d7c288 Compare March 21, 2025 18:03
@oclaw oclaw force-pushed the feature/relayer-fin-ensurer branch 2 times, most recently from a24aec9 to 9d2be0d Compare March 24, 2025 11:25
@oclaw oclaw force-pushed the feature/relayer-tx-sender branch from 2d7c288 to fa2012d Compare March 24, 2025 11:25
rs.Logger.Info().Msg("key generated")
}

// TODO deploy relayer's L2 smart account (if it is not exist)
Copy link
Contributor

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

Copy link
Contributor Author

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

@oclaw oclaw requested a review from akokoshn March 27, 2025 17:49
relayer: recompile l1/l2 ABI
@oclaw oclaw force-pushed the feature/relayer-tx-sender branch from 20ce142 to c4c6fb9 Compare March 28, 2025 15:54
@oclaw oclaw added this pull request to the merge queue Mar 31, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Mar 31, 2025
@oclaw oclaw added this pull request to the merge queue Mar 31, 2025
github-merge-queue bot pushed a commit that referenced this pull request Mar 31, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Mar 31, 2025
@oclaw oclaw added this pull request to the merge queue Mar 31, 2025
Merged via the queue into main with commit 9f6ad7b Mar 31, 2025
15 checks passed
@oclaw oclaw deleted the feature/relayer-tx-sender branch March 31, 2025 09:26
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

Successfully merging this pull request may close these issues.

3 participants