{"id":541,"date":"2023-07-13T16:37:23","date_gmt":"2023-07-13T08:37:23","guid":{"rendered":"https:\/\/www.paralism.com\/info\/docs\/guidelines-for-paralism-node-cli-operation\/node-installation-configuration-and-startup\/"},"modified":"2023-07-13T16:53:49","modified_gmt":"2023-07-13T08:53:49","slug":"node-installation-configuration-and-startup","status":"publish","type":"docs","link":"https:\/\/www.paralism.com\/info\/docs\/guidelines-for-paralism-node-cli-operation\/node-installation-configuration-and-startup\/","title":{"rendered":"Node installation, configuration, and startup"},"content":{"rendered":"\n

Install<\/h2>\n\n\n\n

Visit the official website of the Paralism community https:\/\/www.paralism.com\/<\/a> Obtain the latest version of the software on the node download page. Choose the corresponding software version based on your operating system. The downloaded software may be an executable file of Windows’. exe or a Linux installation file of. rpm, which may be compressed into a. zip file.<\/p>\n\n\n\n

The. exe file can be directly installed under Windows. If your installation files were downloaded from other websites, please be sure to verify whether the software signature information is the official signature of Paralism.com or Hyperchain.net during execution.<\/p>\n\n\n\n

Under Linux, use a terminal to enter the installation file storage directory and execute rpm – ivh parallelism_ Xxx.rpm executes the installation.<\/p>\n\n\n\n

The following will use the Windows version of the Paralism node operation interface as an example to introduce common node operations.<\/p>\n\n\n\n

Configuration and startup<\/h2>\n\n\n\n

Node running parameter settings<\/h2>\n\n\n\n

Enter the CMD command line or Powershell terminal, enter [Disk]: [Paralism installation directory] bin , and create a. cfg configuration file, such as formal.cfg. The common configuration parameters are as follows:<\/p>\n\n\n\n

    \n
  • Me=127.0.1:2000 # Local IP Address and Port<\/li>\n\n\n\n
  • Seedserver=39.104.20.125:8115 # Paralism Public Network Boot Node 1<\/li>\n\n\n\n
  • Seedserver=47.92.69.61:8115 # Paralism Public Network Boot Node 2<\/li>\n\n\n\n
  • With=ledger # Load the general ledger application module<\/li>\n\n\n\n
  • With=paracoin # Load the digital currency application module<\/li>\n\n\n\n
  • Rpcpassword=a # Set rpc port access password<\/li>\n\n\n\n
  • Model=information # Set the network type of node access, where information is the test network and sandbox is the sandbox network.<\/li>\n\n\n\n
  • Rpcallowip=*. *. *. * # Set the whitelist for rpc calls<\/li>\n\n\n\n
  • Disablesafemode=# Set to disable safe mode<\/li>\n\n\n\n
  • Gen=# Set whether to run mining<\/li>\n\n\n\n
  • Restport=8999 # Set the Restful interface service port number of the node<\/li>\n\n\n\n
  • Datadir=E: ParalismNode hc data # Set the directory for storing node data<\/li>\n<\/ul>\n\n\n\n

    The me field specifies the node IP and access port. If it is a node within a local area network, the default specified localhost address does not need to be modified. If the node network card is configured with a public IP address, in order to maximize mining efficiency, it is necessary to set the node IP to the corresponding public IP and accessible port.<\/p>\n\n\n\n

    The seedserver field specifies the boot node required for the node to join the network and synchronize data. It needs to be used in conjunction with the model field, and the configuration reference is as follows.<\/p>\n\n\n\n

    Seedsever<\/td>Model<\/td>Notes<\/td><\/tr>
    47.92.69.61<\/td>informal<\/td>Paralism informal network boot node<\/td><\/tr>
    39.104.20.125<\/td>informal<\/td>Paralism informal network boot node<\/td><\/tr>
    39.100.12.169<\/td>sandbox<\/td>Paralism sandbox network boot node<\/td><\/tr>
    39.100.22.110<\/td>sandbox<\/td>Paralism sandbox network boot node<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Note: When users self-organize a private chain network, two initial nodes are configured and each other is set as the guiding node to achieve private chain deployment.<\/h2>\n\n\n\n

    The with field specifies the loaded application module. At present, the default built-in application module includes the general distributed ledger ledger that can run without mining and the Cryptocurrency paracoin module that can run with mining. Developers can load the required modules as needed. The Paracoin module defaults to loading and running Paralism basic fuel currency Para.<\/p>\n\n\n\n

    Datadir sets the directory for storing node data, which defaults to hc data. The directory contains block information of Cryptocurrency or ledger, module configuration file, node user wallet file and node operation log.<\/p>\n\n\n\n

    Note: <\/strong>It is recommended to store the data in the directory hc when installing node software_ The data and node program directory are stored separately, and the data is regularly backed up to avoid blockchain data loss or wallet data loss caused by program upgrades or system software and hardware failures.<\/p>\n\n\n

    \n
    \"\"
    formal.cfg\u914d\u7f6e\u793a\u4f8b<\/figcaption><\/figure>\n<\/div>\n\n\n

    Startup<\/h2>\n\n\n\n

    After completing the custom configuration file, enter the hc. exe – conf=formal. cfg command at the terminal command prompt to start the node according to the settings. The node process will start with a new terminal window, and when the terminal displays the “hc $” prompt, it indicates that the node software has successfully started and entered the response terminal input command state.<\/p>\n\n\n\n

    To learn about the commands supported by the current node version, enter the help command.<\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    Enter command i to learn about the node code ID and data storage directory of the mining machine.<\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    Note: <\/strong>Closing the terminal window during node operation will cause the node program to exit<\/p>\n","protected":false},"featured_media":0,"parent":534,"menu_order":2,"comment_status":"open","ping_status":"closed","template":"","doc_tag":[],"class_list":["post-541","docs","type-docs","status-publish","hentry"],"comment_count":0,"_links":{"self":[{"href":"https:\/\/www.paralism.com\/info\/wp-json\/wp\/v2\/docs\/541","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.paralism.com\/info\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/www.paralism.com\/info\/wp-json\/wp\/v2\/types\/docs"}],"replies":[{"embeddable":true,"href":"https:\/\/www.paralism.com\/info\/wp-json\/wp\/v2\/comments?post=541"}],"version-history":[{"count":1,"href":"https:\/\/www.paralism.com\/info\/wp-json\/wp\/v2\/docs\/541\/revisions"}],"predecessor-version":[{"id":543,"href":"https:\/\/www.paralism.com\/info\/wp-json\/wp\/v2\/docs\/541\/revisions\/543"}],"up":[{"embeddable":true,"href":"https:\/\/www.paralism.com\/info\/wp-json\/wp\/v2\/docs\/534"}],"next":[{"title":"Mining","link":"https:\/\/www.paralism.com\/info\/docs\/guidelines-for-paralism-node-cli-operation\/mining\/","href":"https:\/\/www.paralism.com\/info\/wp-json\/wp\/v2\/docs\/545"}],"prev":[{"title":"Software and hardware configuration requirements","link":"https:\/\/www.paralism.com\/info\/docs\/guidelines-for-paralism-node-cli-operation\/software-and-hardware-configuration-requirements\/","href":"https:\/\/www.paralism.com\/info\/wp-json\/wp\/v2\/docs\/538"}],"wp:attachment":[{"href":"https:\/\/www.paralism.com\/info\/wp-json\/wp\/v2\/media?parent=541"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/www.paralism.com\/info\/wp-json\/wp\/v2\/doc_tag?post=541"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}