# Startup Arguments

The following arguments can be used to configure your Local Gateway, regardless of the installation method chosen

### Required Gateway Arguments

<table><thead><tr><th>Parameter</th><th>Description</th><th>Example</th><th>Additional notes</th><th data-hidden>Default</th></tr></thead><tbody><tr><td><strong><code>enodes</code></strong></td><td>Enode of the blockchain node</td><td>enode://&#x3C;node_public_key>@&#x3C;ip>:&#x3C;port></td><td>Optional for Enterprise-Elite users or above</td><td>N/A</td></tr><tr><td><strong><code>multiaddr</code></strong></td><td>Node address using p2p nodes format</td><td>/ip4/54.167.71.57/tcp/13000/p2p/16Uiu2HAkvxQyb62x55RrhxxYHm1ZJFMFFFhCZ67YVmTcS6kJwqQR</td><td>Optional for non-Ethereum network or gateway working without blockchain node</td><td>N/A</td></tr></tbody></table>

{% hint style="info" %}
`multiaddr` has replaced `enr` as the argument to indicate the node address because it is human-readable. It has the following format:\
/ip4/\<IPv4\_NETWORK\_ADDRESS>/tcp/\<LISTENING\_PORT>/p2p/\<NODE\_ID>
{% endhint %}

{% hint style="warning" %}
`multiaddr` and `enr` cannot be used at the same time because they represent the same node.
{% endhint %}

### Optional Gateway Arguments

<table><thead><tr><th width="189">Parameter</th><th width="272">Description</th><th width="370">Options/ Additional notes</th><th width="104">Default</th><th width="182">Example</th></tr></thead><tbody><tr><td><strong><code>blockchain-network</code></strong></td><td>Blockchain network the gateway will connect to</td><td>Mainnet, BSC-Mainnet</td><td>Mainnet</td><td>BSC-Mainnet</td></tr><tr><td><strong><code>private-key</code></strong></td><td>Private key for encrypted communication with Ethereum node</td><td>This argument is optional, and the Gateway will generate a random private key if one is not provide.</td><td>N/A</td><td>294549…97dfba3</td></tr><tr><td><strong><code>ws</code></strong></td><td>Enables WebSockets RPC server</td><td></td><td>false</td><td>true</td></tr><tr><td><strong><code>ws-port</code></strong></td><td>WebSockets server port</td><td></td><td>28333</td><td>28334</td></tr><tr><td><p><strong><code>relay-ip</code></strong></p><p>(alias <strong><code>relays</code></strong> )</p></td><td>Specifies relay IP for the gateway to connect to</td><td>Ultra users can provide a list of relays in order to connect to backbone and edge relays from a singular gateway</td><td>N/A</td><td>13.213.141.24</td></tr><tr><td><strong><code>log-file-level</code></strong></td><td>The log level of the log file (found in the <code>logs</code> directory)</td><td>TRACE, DEBUG, INFO, WARN/WARNING, ERROR, FATAL, PANIC</td><td>INFO</td><td>TRACE</td></tr><tr><td><strong><code>log-max-size</code></strong></td><td>Maximum size of a log file (in megabytes) before it is rotated</td><td></td><td>100</td><td>50</td></tr><tr><td><strong><code>log-max-age</code></strong></td><td>Maximum age of an old log file (in days) before it is removed</td><td></td><td>10</td><td>5</td></tr><tr><td><strong><code>log-max-backups</code></strong></td><td>Maximum number of old log files to keep</td><td></td><td>10</td><td>5</td></tr><tr><td><strong><code>port</code></strong></td><td>The external port, which the gateway uses to exchange messages with the relay network</td><td></td><td>1809</td><td>1801</td></tr><tr><td><strong><code>external-ip</code></strong></td><td>The public IP address of the gateway - Please specify your IP address using external-ip if the gateway cannot access the url.</td><td>Use <a href="http://checkip.dyndns.org/">http://checkip.dyndns.org/</a> to automatically detect IP address.</td><td>Automatically tries to find the IP address of the machine</td><td>24.8.18.29</td></tr><tr><td><strong><code>eth-ws-uri</code></strong></td><td>Ethereum WebSockets endpoint for syncing block and transaction content</td><td>You need to configure your Ethereum node to enable the Ethereum WebSockets. For more information see <a href="/pages/-MJmvKcIEm4JZrR2PZEj">Enable Ethereum Websocket</a>.</td><td>N/A</td><td>ws://127.0.0.1:8546</td></tr><tr><td><strong><code>prysm-grpc-uri</code></strong></td><td>Ethereum Mainnet Prysm gRPC uri for getting blocks faster</td><td></td><td>N/A</td><td>IP:Port</td></tr><tr><td><strong><code>beacon-api-uri</code></strong></td><td><a href="https://ethereum.github.io/beacon-APIs/">Beacon API</a> uri used to request blocks using consensus clients standard.</td><td>It requires additional configuration of a consensus client to expose Beacon API.</td><td>N/A</td><td>IP:Port</td></tr><tr><td><strong><code>registration-cert-dir</code></strong></td><td>File path of the private Gateway certificate - It can be a local or remote directory.</td><td></td><td>/ssl</td><td>/usr/local/ssl</td></tr><tr><td><strong><code>txtrace</code></strong></td><td>Enables <a href="/pages/6DnygwFVM0aUZrdjF8F5">TxTrace logging</a></td><td></td><td>false</td><td>true</td></tr><tr><td><strong><code>txtrace-max-file-size</code></strong></td><td>Maximum file size (in megabytes) for TxTrace log files</td><td></td><td>100</td><td>50</td></tr><tr><td><strong><code>txtrace-max-files</code></strong></td><td>Maximum number of TxTrace log files</td><td></td><td>10</td><td>5</td></tr><tr><td><strong><code>disable-profiling</code></strong></td><td>Disables the pprof http server</td><td></td><td>false</td><td>true</td></tr><tr><td><strong><code>blocks-only</code></strong></td><td>Send only paid blocks and transactions to node</td><td></td><td>false</td><td>true</td></tr><tr><td><strong><code>data-dir</code></strong></td><td>Directory to store configuration, status, SSL certificates, and log files</td><td></td><td>/datadir</td><td>/home/[user]/gateway</td></tr><tr><td><strong><code>grpc</code></strong></td><td>Enables gRPC server</td><td></td><td>false</td><td>true</td></tr><tr><td><strong><code>grpc-host</code></strong></td><td>gRPC server host ip address</td><td></td><td>127.0.0.1</td><td>0.0.0.0</td></tr><tr><td><strong><code>grpc-port</code></strong></td><td>gRPC server port</td><td></td><td>5001</td><td>5002</td></tr><tr><td><strong><code>all-txs</code></strong></td><td>Set this flag to propagate all transactions from the BDN to the connected node (warning: may result in worse performance and propagation times).</td><td></td><td>false</td><td>true</td></tr><tr><td><strong><code>enable-blockchain-rpc</code></strong></td><td>Set this flag to enable the gateway to serve as a proxy for your blockchain RPC node.</td><td>Find a detailed guide to using this feature <a href="https://docs.bloxroute.com/introduction/guides/gateway-as-web3-bridge">here</a>.</td><td>false</td><td>true</td></tr><tr><td><strong><code>tx-include-sender-in-feed</code></strong></td><td>Set this flag if you want extract sender of the transaction into Websocket or gRPC feed.</td><td><strong><code>From</code></strong> field is deprecated and will be removed in the future. This made to improve performance and shift responsibility to feed client. In versions up to <code>v2.128.14.1</code> it is <strong>true</strong> by default, after it will be <strong>false</strong>, which means you need to set it explicitly if you want to get <code>from</code>.</td><td>true</td><td><code>--tx-include-sender-in-feed=false</code></td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bloxroute.com/resources/guides/evm-blockchain-distribution-network-bdn/gateway/hosted-and-local-gateways/gateway-installation/startup-arguments.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.