# Startup Arguments

The full lists of startup arguments you may use to configure your Local Gateway. The following arguments can be used to configure your Local Gateway, regardless of the installation method chosen

### Parameters

<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>enodes</code></strong></td><td>Enode of the blockchain node. Example: enode://&#x3C;node_public_key>@&#x3C;ip>:&#x3C;port></td><td>Optional when using Standalone Gateway add-on.</td><td></td><td></td></tr><tr><td><strong><code>blockchain_network</code></strong></td><td>Blockchain network name. </td><td><strong><code>BSC-Mainnet</code></strong> </td><td></td><td></td></tr><tr><td><strong><code>node_validation</code></strong></td><td>Transaction is sent to the blockchain node for validation, and the Gateway returns any error message received in response.</td><td>[Optional]</td><td></td><td></td></tr><tr><td><strong><code>private-key</code></strong></td><td>Private key for encrypted communication with BSC node</td><td>[Optional]</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>[Optional]</td><td>false</td><td>true</td></tr><tr><td><strong><code>ws-port</code></strong></td><td>WebSockets server port</td><td>[Optional]</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>Available with Private Regions add-on</td><td>N/A</td><td>13.213.141.24</td></tr><tr><td><strong><code>log-file-level</code></strong></td><td><p>The log level of the log file (found in the <code>logs</code> directory). Examples:</p><p>TRACE, DEBUG, INFO, WARN/WARNING, ERROR, FATAL, PANIC</p></td><td>[Optional]</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>[Optional]</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>[Optional]</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>[Optional]</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>[Optional]</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>[Optional]. 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>[Optional]. You need to configure your Ethereum node to enable the Ethereum WebSockets. For more information see <a href="broken-reference">Enable Ethereum Websocket</a>.</td><td>N/A</td><td>ws://127.0.0.1:8546</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>[Optional]</td><td>/ssl</td><td>/usr/local/ssl</td></tr><tr><td><strong><code>txtrace</code></strong></td><td>Enables <a href="broken-reference">TxTrace logging</a></td><td>[Optional]</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>[Optional]</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>[Optional]</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>[Optional]</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>[Optional]</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>[Optional]</td><td>/datadir</td><td>/home/[user]/gateway</td></tr><tr><td><strong><code>grpc</code></strong></td><td>Enables gRPC server </td><td>[Optional]</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>[Optional]</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>[Optional]</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>[Optional]</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>[Optional]. 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>[Optional]. <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>