Feat: RPC support (part 1) #177
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
If we launch pre-configured network, like sepolia, the docker trying to overwrite attached default rollup.json, which basically is attached directory
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.
Per the RPC standard, there are several additional RPC endpoints that need to be supported beyond what Magi currently offers, including
version,rollupConfig, andsyncStatus. Furthermore, enhancements togetOutputAtBlockare necessary.The present PR addresses the
versionandrollupConfigendpoints. Subsequent PRs will cover the remaining requirements. Note that I've already implementedsyncStatusin a private fork and would move ASAP.The RPC is important part as batcher uses RPC and by itself it's important to have full
capability.
Also the PR contains fix for docker compose.