Since every block producer is obligated to run a node on the testnet and mainnet, we strongly recommend creating a 'chains.json' file for better visibility and tracking via https://xpr.antelope.tools. Here is a step-by-step guide on how to create the 'chains.json' file: 1. Most BPs already have a 'bp.json' file containing information related to the mainnet. 2. Now, create a second file in the same location as 'bp.json.' This file should have a similar JSON structure, but it should contain data specific to the testnet (endpoints, etc.). 3. In the same directory (and using the same domain you registered for the testnet and mainnet), create a file named 'chains.json.' 4. Enter this JSON code and save it as 'chains.json.' (The important part is the chain ID; the file name can be anything as long as that file exists.) { "chains": { "384da888112027f0321850a169f737c33e53b388aad48b5adace4bab97f437e0": "/bp.json", "71ee83bcf52142d61019d95f9cc5427ba6a0d7ff8accd9e2088ae2abeaf3d3dd": "/xpr-testnet.json" } } Example: We've registered on the testnet and mainnet with the domain alvosec.com and have two files under the home path ('bp.json' and 'testnet.json'). Here's how 'chains.json' should look: https://alvosec.com/chains.json or https://edenia.com/chains.json