Developers
DevelopersGuides
  • Introducing Bond
    • Introduction
    • Why we build Bond?
    • Roles In Bond Ecosystem
    • Decentralised Relations/Social Graph
    • Architecture
    • Bond Reward Model
      • Leech Principle
      • Barrel Principle
  • Main Concepts
    • Bond Profile
      • Identity
      • Relationships
      • Content
      • Creator Economy
    • Connection
      • Connection NFTs
    • Bond Social Graph
    • Centralities
      • In/Out Degree Centrality
      • Betweenness Centrality
      • Closeness Centrality
      • PageRank Centrality
    • Reward Models
    • Reward Contracts
    • Off-chain Oracles
    • Gasless Mode
    • Cross Chain Messaging and Pay Gas with Bond Token
  • Bond API
    • Introduction
    • API Urls
    • Getting started with GraphQL
    • Authentication
      • Login
      • Refresh JWT
    • Profile
      • Create Profile
      • SetProfileMetadata
    • Connect
      • Connect a profile
      • Disconnect
  • Smart Contracts
    • BondHub
    • MerkelDistributor
    • TokenDeployer
    • SingleStakePoolDeployer
    • LzTokenDeployer
    • LzSingleStakePoolDeployer
  • Bond SDK
    • Bond JS SDK
      • Authenticate
      • Create Profile
      • Connect
  • Bond Nodes
    • Hardware Requirements
    • Set up and Deploy
    • Node Config (TOML)
    • Secrets Config (TOML)
    • Role-Based Access Control (RBAC)
  • References
    • Deployed Contracts
    • Github
Powered by GitBook
On this page
  1. Bond Nodes

Hardware Requirements

To effectively run a Bond Oracle node, both hardware and software requirements vary based on the volume of jobs your node undertakes. Here's a streamlined guide for setting up your node.

System Requirements:

  • Development: For those starting out or in a testing phase, systems should have a minimum of 2 CPU cores and 4 GB of RAM. Apple M1 systems are suitable for this stage if you're operating the Bond Oracle node within Docker.

  • Production: Nodes that handle over 100 tasks should be equipped with at least 4 CPU cores and 8GB of RAM. When using a PostgreSQL database on the same machine, it's advised to have a setup with at least 4 cores, 16 GB of RAM, and 100 GB storage.

If you're considering cloud deployments, choose instances with dedicated core allocations, especially on platforms like AWS. Shared core instances or those offering burstable performance could compromise the node's performance.

Software & Connectivity:

  • Operating System: Bond Oracle nodes run on Linux, MacOS, and WSL. However, for serious deployments, Linux is advised.

  • Docker & PostgreSQL: It's most efficient to use Bond's Docker Images, especially the non-root variants. The database versions that play well with Bond range from 11 to 15.

When it comes to interfacing with blockchains, a fully synchronised network client is essential. Depending on the blockchain (like Ethereum), you'd need specific clients. The chosen client should:

  • Offer both HTTP and WebSocket connections with SSL security.

  • Be hosted either via providers like Alchemy/Infura or on a personal setup for better control and reduced latency.

  • If self-hosted, use a web server like Nginx to manage SSL encryption and facilitate the connection between the server and client.

For more in-depth information on interfacing with Ethereum or other blockchains, it's advisable to consult the respective detailed guides.

PreviousConnectNextSet up and Deploy

Last updated 1 year ago