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

Support multiple input sources #157

Open
endersonmaia opened this issue Feb 17, 2025 · 2 comments
Open

Support multiple input sources #157

endersonmaia opened this issue Feb 17, 2025 · 2 comments
Labels

Comments

@endersonmaia
Copy link
Contributor

endersonmaia commented Feb 17, 2025

To provide inputs comming from espresso, an --enable-espresso cli argument is being developed.

With --enable-espresso cli will disable the evm-inputreader and start a cartesi-espresso-reader together with a espresso-dev-node so the developer can work with inputs comming from espresso.

That being said, imagining a future where cartesi support multiple inputs sources, we'd get into a place where we could have a lot of --enable-<input-source>

Proposal

Add a --input-source = [ evm * | espresso | avail | ... ] (* default).

According to the input source defined, the infrastructure needed to use that input source should be started, like an espresso-dev-node and espresso-reader for --input-source=espresso, for ex..

@endersonmaia
Copy link
Contributor Author

This may also impact how the cartesi send command will work with the new input sources.

@tuler
Copy link
Member

tuler commented Mar 6, 2025

I think a better term, is case of espresso, is sequencer, instead of input-source.

You would do cartesi rollups start --sequencer espresso

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants