Skip to content
You are reading Tessera development version documentation and some displayed features may not be available in the stable release. You can switch to stable version using the version box at screen bottom.

Configure peer discovery

You can configure peer discovery in the Tessera configuration file. Configuration options for peer discovery are:

Disable peer discovery

You can disable peer discovery by setting disablePeerDiscovery in the configuration file to true. If peer discovery is disabled, communication is limited to specified peers. Communication from nodes not listed as a peer is ignored. Peer discovery is enabled by default.

Disable peer discovery configuration

"disablePeerDiscovery": true


Disabling peer discovery does not stop incoming transactions from nodes that are not in the peer list. To stop transactions being received from nodes that are not in the peer list, enable the allowlist option.

Specify peers

You can specify a list of Tessera node URLs used by Tessera to discover other nodes. Specify the peer list using peer in the configuration file.

Peer list configuration

"peer": [
    "url": ""
    "url": ""
    "url": ""


When your node starts up, these are the peers it will search for. Include multiple peers in the peer list in case any of them are offline or unreachable.

Enable allowlist

The Tessera allowlist (whitelist) restricts connections for Tessera in the same way the permissioned-nodes.json file does for GoQuorum.

Set useWhitelist in the configuration file to true to indicate that only specified peers can connect or submit transactions.

Enable allowlist configuration

"useWhiteList": true,

Enable remote key validation

Remote key validation checks that a remote node owns the public keys being advertised. Enable remote key validation by setting enableRemoteKeyValidation in the configuration file to true. Remote key validation is disabled by default.

Enable remote key validation configuration

 "features": {
   "enableRemoteKeyValidation": true


We recommend enabling remote key validation to prevent malicious attacks. The default configuration is false because this is a breaking change for Tessera versions before v0.10.0.

ConsenSys has acquired Quorum from J.P. Morgan. Please read the FAQ.
Questions or feedback? You can discuss issues and obtain free support on Tessera Slack channel.