Node Setup Instructions

Get your node up and running in just a few minutes on your computer.

Signing up for the Beta

We're excited to provide early access to those interested in running a node to help power Presearch, the decentralized search engine. More than 4,000 nodes are already being operated by beta testers, and these nodes provide the infrastructure for the Presearch Engine Testnet, which can be searched via: https://testnet-engine.presearch.org.

If you'd like to join the beta program and run a Presearch node, you can sign up at: https://presearchcommunity.typeform.com/to/UkDumktm

You will be notified once you are approved, at which point you can follow the below instructions to get your node up and running. The below instructions WILL NOT WORK until you've been accepted into the Beta program (you will be redirected back to the Presearch Nodes Beta Signup Form in that case).

Setup Instructions

If you have any questions, you can join our helpful nodes telegram group.

1. Install Docker on your computer or virtual server (or use a turn-key solution like ThreeFold.io that has support for launching Presearch nodes already built into the platform)

2. Get your node registration code at https://nodes.presearch.org/dashboard.

3. Run the node start commands below in your terminal to install your node [ See tutorials for how to open terminal on Mac & Windows ]

Copy/Paste the operating-system-specific command below into your terminal:

Linux/Mac
Windows
Linux/Mac
docker stop presearch-node ; docker rm presearch-node ; docker stop presearch-auto-updater ; docker rm presearch-auto-updater ; docker run -d --name presearch-auto-updater --restart=unless-stopped -v /var/run/docker.sock:/var/run/docker.sock containrrr/watchtower --cleanup --interval 300 presearch-node ; docker pull presearch/node ; docker run -dt --name presearch-node --restart=unless-stopped -v presearch-node-storage:/app/node -e REGISTRATION_CODE=$YOUR_REGISTRATION_CODE_HERE presearch/node ; docker logs -f presearch-node

Windows
docker stop presearch-node & docker rm presearch-node & docker stop presearch-auto-updater & docker rm presearch-auto-updater & docker run -d --name presearch-auto-updater --restart=unless-stopped -v /var/run/docker.sock:/var/run/docker.sock containrrr/watchtower --cleanup --interval 300 presearch-node & docker pull presearch/node & docker run -dt --name presearch-node --restart=unless-stopped -v presearch-node-storage:/app/node -e REGISTRATION_CODE=$YOUR_REGISTRATION_CODE_HERE presearch/node & docker logs -f presearch-node

IMPORTANT: You must insert your registration code from step #2 above into the script by replacing the text$YOUR_REGISTRATION_CODE_HEREwith your actual registration code. So, for example, if your registration code is XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX then the final command would contain the text REGISTRATION_CODE=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX .

The above command installs two services on your computer, the presearch-node and the presearch-auto-updater, and configure both of them to be always running in the background.

The presearch-node actually runs the decentralized search software, whereas the presearch-auto-updater is responsible for automatically upgrading the presearch-node to the newest versions when released to ensure the node stays up to date and can continue to connect to the Presearch network.

Running Searches

Keep an eye on the running node output and you’ll eventually see incoming searches (“Success! ...”). You can run searches yourself at https://testnet-engine.presearch.org, though keep in mind these will be distributed across all nodes in the Testnet, not just yours.

Managing your Node

The command in the setup instructions configured your node to run as a background service. This means you can close your terminal and it will continue running as long as your system is up and haven't manually stopped your node.

If you would like to see the output of your node at any point you can run the following command:

See current node output: docker logs -f presearch-node

To stop your node and the presearch-auto-updater manually, run the following commands in your terminal:

Manually stop your node: docker stop presearch-node docker stop presearch-auto-updater

To restart a manually-stopped node, run the following command:

Restart your stopped node: docker start presearch-auto-updater docker start presearch-node

If you would like to see if your node or the presearch-auto-updater are running, run the following command: Check if the node services are running: docker ps

Finally, if you run into any problems with your node, you can always run the installation script again from the setup instructions section if needed. Your node identity will be preserved, but should will get your node upgraded, reinstalled, and over most configuration issues you may encounter.

Hardware Specification

  1. Docker image is only for x86 / x64 based CPU's for now.

  2. We plan to support ARM / Raspberry Pi in the future, but we're currently focused on fixing bugs and making sure the current platform is robust before additional supported platforms.

Running Multiple Nodes

You are more than welcome to run as many nodes as you would like under your Presearch account. You can reuse the same Registration Code to launch each node, subject to the following limitations:

  • You may only run one node per server at a time. Presearch will only allow one connection per IP address at the same time, so if you want to disconnect a second node from the same IP address you’ll need to stop the other node first.

  • You must include a valid Registration Code on the first run of each node to initialize it and attach it to your Presearch account. When the node software runs for the first time, it creates a public/private key pair to uniquely identify your node on subsequent requests.

  • You can optionally change your Registration Code at any time by clicking "Generate Replacement Code" on the Nodes Dashboard. Any prior nodes initialized with the old Registration Code will continue to work, but the old code will no longer be able to initialize any new nodes.

  • You may not run the same node simultaneously on multiple servers. If you initialize a node and then copy the initialized node to another server (which transfers the node’s unique public/private key identifiers), this creates a copy of the same node identity on both servers. If you try to run both at the same time, the Presearch Engine will reject the second one until the first disconnects.