DigiOracle Docs v1.0.1
  • 📔KlayOracle Documentation
  • Fundamentals
    • Introduction
    • Architecture
    • Aggregation Mechanism
    • Node & data provider communication
    • Installing KlayOracle
  • Smart Contract Developers
    • Price Feeds
      • Quick Start: Code Samples
      • How to Use KlayOracle Price Feeds
    • Random Number Generator
      • Quick Start: Code Samples
      • How to Use KlayOracle Random Number Generator
  • Data Providers
    • Introduction
    • Install & run data providers locally
    • How It Works
      • Configuring Data Feeds
      • Reducers
      • Data provider utilities
      • Configuration Files & Environmental Variables
      • OracleProvider Contract
      • Bootstrap Data Providers
    • Best Practices
  • Nodes
    • Introduction
    • Install & run node locally
  • Community
    • DigiOracle Champion Program
      • About the DigiOracle Champion Program
      • How to create content & become a DigiOracle Champion
      • Contribution Guidelines
      • FAQs
    • Bounties
Powered by GitBook
On this page
  1. Nodes

Install & run node locally

PreviousIntroductionNextDigiOracle Champion Program

Last updated 1 year ago

This section is currently being developed. To contribute, open a pull request on the .

  • Generate a selfsigned certificate for each node. .

  • Use different authority or wildcard matching authority of each node you intend to run.

  • In node/config.yml, set the key and the pem you used to generate the certificate.

  • Give the certificate pem file to data providers for authenticating with your Node. You can also run your own data providers.

  • Update your organization details in node/config.yml. Website must match authority used to sign certificate, an example will be if authority is *.origineum.com, website can be node-1.origineum.com. Otherwise, node service will fail to start.

  • In .env, HOST_IP is the dns for reaching your node. If you're running a docker container, you can override it and other env variable by passing from terminal.

  • In .env PRIVATE_KEY is your Node signer with enough Klay tokens to pay for request.

  • In .env COCKROACH_DNS_URL is your full connection string to cluster. A free account will suffice for a considerable period.

  • In .env OAUTH_TOKEN is the Oauth token given to data providers using your Node.

  • Run make gomodtidy, make node-tables, make node-server-nolog HOST_IP=0.0.0.0:50054 or make node-server HOST_IP=0.0.0.0:50054 on your local machine to test it locally.

documentation GitHub repo
see guide using open ssl
https://cockroachlabs.cloud/