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
When we launch a shared sequencer stack and an evm rollup using the helm charts in charts directory. It is not explicit on what the URL of the sequencer RPC is and also of the execution RPC of the evm rollup and the WSS RPC of the evm rollup.
It would be great if we could document these things better, so that developers developing against the shared sequencer stack can have an easier time doing integration testing.
The text was updated successfully, but these errors were encountered:
…ocs (#888)
## Summary
Add information on the Sequencer and EVM rollup endpoints in the
README.md of the dev-cluster charts in the `charts` directory.
## Background
When launching applications which are built on top of the shared
sequencer like Composer. We require the URL of the shared sequencer RPC
which requires some digging into k8s ingresses to get.
This PR explicitly adds it to the doc.
## Changes
- Update the docs to include the sequencer and evm rollup endpoints.
## Testing
no testing required since these a documentation changes.
## Related Issues
#886
closes <!-- list any issues closed here -->
When we launch a shared sequencer stack and an evm rollup using the helm charts in
charts
directory. It is not explicit on what the URL of the sequencer RPC is and also of the execution RPC of the evm rollup and the WSS RPC of the evm rollup.It would be great if we could document these things better, so that developers developing against the shared sequencer stack can have an easier time doing integration testing.
The text was updated successfully, but these errors were encountered: