Static ip and port and modified kurtosis fork usage (for exex L2 RPC endpoint) #33
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
adaki2004
changed the title
Brechtpd
reviewed
Aug 23, 2024
Brechtpd
approved these changes
Aug 31, 2024
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.
@Brechtpd we have a working L2 exex rollup, and at least one open communication channel thru rpc.
You can use the
make install, makepropose number=1and then query the RPC as you can see above.Still thinks to be considered what is the best way to set the IP+Port because now i'm hard-coding it. Shall it be an input param ? (paradigmxyz#10443 (comment))
(For me next is the builder & submit to L1.)