Skip to content
You are reading GoQuorum 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.

Node discovery

Tessera uses peer discovery to discover Tessera nodes in the network. Tessera nodes share their entire peer lists, enabling new nodes to discover all nodes in the network. When sharing their peer lists, Tessera broadcasts the public keys for each node and the list of URLs with which each node has current active communication.

Tessera maintains two node lists, PartyStore and NetworkStore. NetworkStore lists nodes with which an active connection has been established. PartyStore lists URLs from the peer entry in the Tessera configuration file and URLs discovered from remote nodes. If Tessera can’t communicate with a node, the peer is removed from both the PartyStore and NetworkStore lists.

If all peers are removed from the PartyStore and NetworkStore lists, the PartyStore list is repopulated from the peer entry in the Tessera configuration file. A dropped remote peer is added to the NetworkStore list only after establishing direct communication with the peer. That is, discovering a dropped remote peer is not enough for a node to be added to the active peer list.

The partyinfo API method returns nodes with which Tessera has a current active connection (that is, nodes listed in NetworkStore).

Configure peer discovery in the Tessera configuration file.

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.
For paid professional support by ConsenSys, contact us at [email protected]