You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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>
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..
The text was updated successfully, but these errors were encountered:
To provide inputs comming from espresso, an
--enable-espresso
cli argument is being developed.With
--enable-espresso
cli will disable theevm-inputreader
and start acartesi-espresso-reader
together with aespresso-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
andespresso-reader
for--input-source=espresso
, for ex..The text was updated successfully, but these errors were encountered: