The pendingTxs stream can use Local Ethereum(or other EVM-compatible networks) Node Validation to achieve the best performance. This validation doesn't apply to the newTxs stream.
If you are using the pendingTxs stream with a Gateway and your node is configured to publish feeds, the Gateway can perform additional verification by subscribing to the Ethereum node’s websocket feeds (newPendingTransactions and newHeads).
If the Ethereum node does not publish these feeds, the Gateway will still provide the newBlocks stream and pendingTxs stream, but performance may not be optimal. It’s best to enable this support by doing the following.
Enabling Ethereum Websocket Feeds and Connecting the Gateway to the Ethereum Node Websocket Server
1. Start your Ethereum node with the following parameters:
--ws.addr<ETH node IP address>
Replace <ETH node IP address> above with your Ethereum node’s IP address. Ethereum’s websocket server will only allow connections to that IP.
If you change the port, then make sure to use the same port in the Gateway startup parameters.
2. To instruct the Gateway to connect to the Ethereum node websocket server, start the Gateway with the following arguments in addition to the regular startup parameters:
--eth-ws-uri ws://<ETH node IP address>:8546
Replace <ETH node IP address> above with your Ethereum node’s IP address. If your Gateway is running on a different machine than your Ethereum node, use the public IP of the machine that hosts the Ethereum node. If your Gateway and Ethereum node are running on the same machine, use the local host: --ws.addr 127.0.0.1 for the Ethereum Node and--eth-ws-uri ws://127.0.0.1:8546 for the Gateway.