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

Tooling to deploy nitro integration on top of espresso sequencer #144

Open
2 tasks
sveitser opened this issue Jul 10, 2024 · 1 comment
Open
2 tasks

Tooling to deploy nitro integration on top of espresso sequencer #144

sveitser opened this issue Jul 10, 2024 · 1 comment
Assignees

Comments

@sveitser
Copy link
Collaborator

sveitser commented Jul 10, 2024

It's difficult to debug issues our partners run into when deploying nitro. We should have a reference for deploying nitro on top of our Espresso sequencer cloud deployments. It does not need to be a persistent deployment immediately because we don't strictly need or want to run a persistent deployment ourselves.

If we can provide this we can

  1. identify issue nitro operators may face earlier and fix them
  2. reduce the chances of misconfiguration because nitro operators have a reference to refer to

A minimal implementation could be a script to generate config files (if necessary), deploy contracts and run the nitro services.

Cappuccino deployment details are here: https://www.notion.so/espressosys/Cappuccino-Deployment-Info-5ea5e4b000b947859eca326457811843

Deliverables

  • Executable reference code to deploy a nitro node with Espresso Integration on top of our Cappuccino cloud deployment.
  • Light documentation on how to use it.
@sveitser
Copy link
Collaborator Author

sveitser commented Jul 10, 2024

We did something similar before for a bridge demo and the code for that is here EspressoSystems/nitro-testnode#19

We may be able to borrow some of that code. We should also check if upstream provides some tooling for this.

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

No branches or pull requests

2 participants