-
Notifications
You must be signed in to change notification settings - Fork 8
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
submit new l2 blocks using RPC #28
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mskrzypkows
changed the title
submit_new_l2_blocks implemented
submit new l2 blocks using RPC
Jun 25, 2024
smartprogrammer93
approved these changes
Jun 25, 2024
Node/src/taiko/mod.rs
Outdated
@@ -20,8 +20,12 @@ impl Taiko { | |||
.await | |||
} | |||
|
|||
pub fn submit_new_l2_blocks(&self) { | |||
pub async fn submit_new_l2_blocks(&self, value: Value) -> Result<Value, Error> { |
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.
Lets call this method advance_head_to_new_l2_block
or just advance_head
because submit
might be confused with submit to block to L1
every 4 seconds and not blocked by channel processing Co-authored-by: Ahmad Bitar <[email protected]>
fixed some JSON RPC compatibility with taiko-clients
…econf-AVS-Node into move_the_head_rpc
mskrzypkows
added a commit
that referenced
this pull request
Jul 7, 2024
* RPC client for fetching tx lists (#23) * RPC client for fetching tx lists RPC server for tests * Improve async processing and error handling * More assert to the gen l2 tx test --------- Co-authored-by: Denis Kolodin <[email protected]> Co-authored-by: Ahmad Bitar <[email protected]> * submit new l2 blocks using RPC (#28) * submit_new_l2_blocks implemented * fixed tests * Fix loops in Node/src/node/mod.rs to be consistent (#38) every 4 seconds and not blocked by channel processing Co-authored-by: Ahmad Bitar <[email protected]> * Two RCP addresses for the Node fixed some JSON RPC compatibility with taiko-clients * unused import * small fixes --------- Co-authored-by: Ahmad Bitar <[email protected]> Co-authored-by: Ahmad Bitar <[email protected]> * Unit test for deployment and call of Ethereum contract (#39) * Unit test for deployment and call of Ethereum contract * foundry for github actions * propose_new_block call with empty parameters * Default params for the newBlockProposal * rest parameter passed to the propose_new_block * Send new block proposal by raw tx (#47) * build Eip1559 transaction * Handling additional arguments passed by JSON RPC from proposer * Forwarding of encoded tx to the mev boost module * Configuration parameters take form the ENV * sending new block proposal using builder.send * renamed according to the review --------- Co-authored-by: Denis Kolodin <[email protected]> Co-authored-by: Ahmad Bitar <[email protected]> Co-authored-by: Ahmad Bitar <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.