mobilecoin-consensus-fog
  • Consensus Server Runbook
  • About
    • About this Runbook
      • Audience
        • How to Use This Information
  • Common Tasks
    • About Common Tasks
  • Understanding the Consensus Server
    • Secure Enclaves
  • Prerequisites
    • IAS Account
    • SGX-Enabled Machine
  • Getting Intel Attestation Service Credentials
    • Quote Status Responses
    • Validating the Attestation
  • SGX Provisioning
    • Provisioning with Azure
    • Downloading the Consensus Server Software
      • Downloading the Pre-Built Container from Docker Hub
  • Running the Node
    • Running the Node in a Container (Preferred Method)
      • Environment Variables: How to Configure Your Node
      • Run It!
    • Using Your Own Binaries (Without Docker)
      • Run It!
  • Upgrading the Enclave
    • Unacceptable Degradation of Service
    • Uneven Node Block Heights
    • Monitoring
  • Configuring your Node
    • Configuring your Node to Connect with Trusted Peers
      • Broadcasting to Trusted and Untrusted Peers
      • Defining a Consensus Quorum Set
      • Obtaining Ledger Contents from S3 Archive for Catchup
    • Signing Consensus Messages
    • Distributing Ledger Contents to S3 Archive
    • Obtaining the Origin Block
    • Updating Your Network Configuration
  • Attesting to the Consensus Server
  • Proposing Transactions
  • Verifying Transactions are Working Correctly
    • Send Transaction
    • Use the Python API to Check Balance and Send Transactions
    • Verify Nodes are Participating in Consensus
  • Common Errors and Alerts
    • Common Errors
    • Common Alerts
  • Glossary
    • Glossary
  • Frequently Asked Questions (FAQs)
    • FAQs
Powered by GitBook
On this page
Edit on GitHub
  1. Configuring your Node
  2. Configuring your Node to Connect with Trusted Peers

Broadcasting to Trusted and Untrusted Peers

The broadcast_peers define the nodes to which your node will broadcast messages.

MobileCoin uses Universal Resource Identifiers (URIs) to specify peers. These include the address of the peer, the peer's public key, and can optionally include connection information, such as the certificate authority bundle, and tls-hostname.

The URIs indicate the following:

URI Component
Value
Function

Scheme

mcp or mcp-insecure

Determines whether to use tls in the connection to the peer. Most often, these will be mcp.

Address and Port

Address of node and peer listening port

DNS address and listening port of the consensus peer.

consensus-msg-key query parameter

The public message signer key of the peer.

This is verified against every message from that peer to ensure it was signed by the peer you expect.

PreviousConfiguring your Node to Connect with Trusted PeersNextDefining a Consensus Quorum Set

Last updated 3 years ago