MetaHash network consists of many servers grouped into roles within the network. There are several networks based on the TraceChain technology which are named as TestNetwork (TMH network) and ProductionNetwork (MHC network).
Test and Production networks
TestNetwork in the MetaHash network is presented as net-dev and net-test. ProductionNetwork is marked as net-main. Any Metahash network allows to view the full digital ledger of transactions, it is possible by means of explorers developed for this purpose. All the explorers are provided with search by address, hash transaction or block number in Blockchain for the sake of user convenience.
All networks work with a large number of various servers playing different roles: peer node, verifier, core or torrent. Each role has its own identification name in the network.
Each network has its DNS address allowing to see the full list of available servers of any role. Address is created on the basis of server role and network name. For example, torrent server addresses for the nest network can be accessed at domain address tor.net-test.metahashnetwork.com, where the first part “tor” indicates that it is required to return the list of torrent servers, and the second part of the “net-test” address shows that the list of servers will be created for the test network net-test. Address of proxy servers for production network will be accessed at DNS address proxy.net-main.metahashnetwork.com. Using this example you can get the list of all servers of any role in any Metahash network1.
Please note that all torrent servers in Metahash networks respond to port 5795. Proxy servers in TestNetwork as well as in ProductionNetwork respond to port 9999.
Using DNS addresses
In order to use DNS addresses for getting proxy and torrent servers addresses in one of the networks, it is needed to use one of the utilities included into BIND package for UNIX systems: nslookup, dig or host. nslookup tool is also ported to Windows OS. These utilities are a DNS client that provides user with a command-line interface for accessing DNS system.
Examples of using DNS addresses2
In test network net-dev
|host tor.net-dev.metahashnetwork.com|| ;; Truncated, retrying in TCP mode.
tor.net-dev.metahashnetwork.com has address 184.108.40.206
tor.net-dev.metahashnetwork.com has address 220.127.116.11
and the full list of torrent servers of the test network net-dev.
|nslookup proxy.net-dev.metahashnetwork.com|| Name: proxy.net-dev.metahashnetwork.com
and the full list of proxy servers of the test network net-dev.
In test network net-test
|host tor.net-test.metahashnetwork.com|| tor.net-test.metahashnetwork.com has address 18.104.22.168
tor.net-test.metahashnetwork.com has address 22.214.171.124
and the full list of torrent servers of the test network net-test.
In production network
; <<>> DiG 9.8.1-P1 <<>> proxy.net-main.metahashnetwork.com
tor.net-main.metahashnetwork.com has address 126.96.36.199
1 Not all server addresses are currently published
2 IP list in DNS is constantly changing. Please don’t use server addresses given here as examples, instead make request to DNS on your own immediately before working with Metahash network.