Open emhane opened 1 year ago
What do these tasks entail? If I am looking at the tendermint clients correctly then the difference is simply passing in a wss://
url rather than a ws://
and let them handle everything.
Is there anything that we should do implementation wise in our services to unblock this? Or is this infra work? https://github.com/astriaorg/infra and https://github.com/astriaorg/dev-cluster
What do these tasks entail? If I am looking at the tendermint clients correctly then the difference is simply passing in a
wss://
url rather than aws://
and let them handle everything.exactly, nothing else in the rust code to do
Is there anything that we should do implementation wise in our services to unblock this? Or is this infra work? https://github.com/astriaorg/infra and https://github.com/astriaorg/dev-cluster
possibly update docs and comments. local.env.example files need to be updated, probably testnets scripts in this repo @WafflesVonMaple. setting up certificate can move to dev cluster repo.
We use secure connections as needed in production and are supported it's just not done for local instances for testing environments
running a rollup node and cometbft full node on separate machines greatly decrease hardware requirements to interact with and run the shared-sequencer. the modular design of astria components allows for this.
next step, is to upgrade communication between conductor and cometbft node as well as sequencer-client (composer) and cometbft node to use the wss scheme and https scheme respectively. tendermint-rs web socket supports wss urls.