Welcome to Presearch Nodes Beta!
We’re excited that you’re here. If you want to try running a node, join our telegram (https://t.me/PresearchNodes) & fill our the Typeform (https://presearchcommunity.typeform.com/to/UkDumktm) for beta here & we’ll approve you! Node rewards going live soon so you will earn on your crypto!
Search engines are complicated, and building a decentralized search engine provides some unique challenges which do not apply to centralized search engines. For example: how do you prevent malicious actors from running nodes and either stealing user information or returning dangerous or unwanted content? How do you get fast (hundreds of milliseconds) response times across a massively distributed network of servers with drastic variability in performance and reliability? How do you properly incentivize people to run nodes and fairly balance supply and demand for both nodes and searches within the network? Some of these issues Presearch has already solved, and some will require continued experimentation and innovation over time, but Presearch will roll out both the platform and the decentralization of the platform incrementally to ensure an optimal ongoing search experience for the amazing Presearch community.
There are six core layers of the Presearch search engine architecture:
• Core Services: Advertising API, Account Management API, Search Rewards Tracking, Keyword
Staking, Marketplace, and other critical Presearch services which are centrally managed by Presearch.
• Web Server: Receives Search Requests from Presearch users and passes them on to the Gateway to
generate results. Returns a final, rendered results page to the user.
• Node Registry: Manages the identity of all nodes, node stats, and any rewards payouts to node
• Node Gateway: Receives requests from the Web Server, removes personally identifiable information
from the search requests, and passes the search to one or more healthy nodes.
• Nodes: Decentralized search “workers” which connect to the Node Gateway and perform search
operations. Each node is required to have a unique publicly-facing IP address.
• Search Packages: Open source plugins which return intelligent answers and info boxes in response
to specific queries. The following diagram shows the interactions between the major components
within the Presearch Search Architecture.
We’re excited you’re here and can’t wait to watch you search with PRE!
– Alex Carrabre