We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When connecting the bridge node to the consensus node running on localhost, I believe we should explicitly enable the gRPC configuration in config/app.toml. It's relevant to the step described in https://docs.celestia.org/nodes/validator-node#run-the-bridge-node and closely related to https://docs.celestia.org/nodes/full-consensus-node#expose-rpc
localhost
config/app.toml
Initialize the bridge node
Optional: Configuring an RPC endpoint
If that makes sense, I'd create a PR to modify the documents!
The text was updated successfully, but these errors were encountered:
makes sense! thank you @tksohishi
Sorry, something went wrong.
gm @tksohishi do you still want to add this?
No branches or pull requests
Problem
When connecting the bridge node to the consensus node running on
localhost
, I believe we should explicitly enable the gRPC configuration inconfig/app.toml
. It's relevant to the step described in https://docs.celestia.org/nodes/validator-node#run-the-bridge-node and closely related to https://docs.celestia.org/nodes/full-consensus-node#expose-rpcProposed changes
Initialize the bridge node
Optional: Configuring an RPC endpoint
section to mention the configuration aboveIf that makes sense, I'd create a PR to modify the documents!
The text was updated successfully, but these errors were encountered: