Peering with xlm.sh nodes

xlm.sh utilizes self-hosted IPFS nodes to accelerate user access to content, providing a seamless and efficient decentralized storage experience. By establishing direct connections with our nodes, you can significantly enhance the speed and reliability of your data retrievals.

How Peering Works

When an IPFS node requests data, it broadcasts a message to its connected peers. If none of these peers hold the requested Content Identifier (CID), the node searches the Distributed Hash Table (DHT) for Provider Records that indicate which nodes are hosting the desired data. Directly peering with xlm.sh nodes ensures that your IPFS node has immediate access to the necessary data without the need for extensive DHT queries, resulting in reduced latency and improved responsiveness.

Benefits of Peering with xlm.sh Nodes

Faster Access: Maintain persistent connections to xlm.sh nodes to achieve lower latency in data retrieval.
Improved Reliability: Enhance the reliability of your IPFS node by leveraging the robustness of xlm.sh’s infrastructure.
Efficient Resource Utilization: Optimize your node’s performance by reducing the overhead associated with DHT lookups.

Peering Configuration

To integrate peering with xlm.sh nodes, configure your IPFS node to prioritize connections to our nodes. Below is an example configuration for kubo, the primary Go implementation of IPFS:

json

{
  "Peering": {
    "Peers": [
      {
        "Addrs": ["/dnsaddr/alice.ipfs.xlm.sh"],
        "ID": "12D3KooWAUrkQQxX7KXCPjxPRMj82h5LQLNWMLDkPbFGTHqYMsdy"
      },
      {
        "Addrs": ["/dnsaddr/bob.ipfs.xlm.sh"],
        "ID": "12D3KooWFeQUCoAC1DseHPZtGN7MGZTumadyv3xR9RDhhaBpTX35"
      }
    ]
  }
}

Steps to Configure Peering:

Locate Your IPFS Configuration File
Typically found at ~/.ipfs/config.
Add the Peering Section:
Insert the above JSON snippet into your configuration file under the appropriate section.
Restart Your IPFS Node:
Apply the changes by restarting your IPFS daemon:
shell
```
ipfs daemon
```

Using Different IPFS Implementations

If you are using an IPFS implementation other than kubo, refer to your specific node’s documentation for instructions on configuring peering. Use the following address and Peer ID for xlm.sh:

Node Name	Address	Peer ID
Alice	`/dnsaddr/alice.ipfs.xlm.sh`	`12D3KooWAUrkQQxX7KXCPjxPRMj82h5LQLNWMLDkPbFGTHqYMsdy`
Bob	`/dnsaddr/bob.ipfs.xlm.sh`	`12D3KooWFeQUCoAC1DseHPZtGN7MGZTumadyv3xR9RDhhaBpTX35`

For more examples and a list of other content providers you might want to peer with, see Peering with content providers.

Peering with xlm.sh nodes ​

How Peering Works ​

Benefits of Peering with xlm.sh Nodes ​

Peering Configuration ​