Skip to content

Union Node Configuration

Connor Davis edited this page Apr 25, 2024 · 6 revisions

While the public Union docs contain many recommendations for node configuration, this document aims to supply devs with configuration options and advice to resolve common errors in our developer experience.

Resolving request body too large

To ensure large request aren't denied, like when uploading a light client, you should ensure three options are large enough on the node. Once the node you're submitting transactions to is configured with these options and restarted, your request should go through without being rejected.

  1. Inside config.toml under the rpc table, we should change max_body_bytes to something larger: 10000000 (~10 MB)
# Maximum size of request body, in bytes
max_body_bytes = 10000000
  1. Inside config.toml under the mempool table, we should change max_tx_bytes to something larger: 10000000 (~10 MB)
# Maximum size of a single transaction.
# NOTE: the max size of a tx transmitted over the network is {max_tx_bytes}.
max_tx_bytes = 10000000
  1. Inside app.toml under the api table, we should change rpc-max-body-bytes to something larger: 10000000 (~10 MB)
# RPCMaxBodyBytes defines the CometBFT maximum request body (in bytes).
rpc-max-body-bytes = 10000000