forked from OffchainLabs/nitro-testnode
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add E2E tests for partner architectures #56
Comments
sveitser
changed the title
Add E2E tests for architectures
Add E2E tests for partner architectures
Oct 1, 2024
The arch for altlayer should be
Sequencer is the feed source for everyone. Only fullnode(s) handle RPC requests, and their forwarding target is set to sequencer. One thing we currently don't have I think is a separate batch poster service. So this needs to be added. |
We should also do this for an L3. |
sveitser
changed the title
Add E2E tests for partner architectures
Add E2E tests for L3 deployment & partner architectures
Oct 1, 2024
sveitser
changed the title
Add E2E tests for L3 deployment & partner architectures
Add E2E tests for partner architectures
Oct 1, 2024
The arch for caldera should be
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We want to make sure that our nitro integration can be deployed by our partners. To do that we will deploy test-node mimicking our partners configure their nitro architecture.
We explicitly are not looking to do a persistent deployment so it's enough to start the nodes, assert they are working and shut them down. We might also run them for longer periods (days).
The text was updated successfully, but these errors were encountered: