CARV
CARVPlayPortalProtocol
  • Overview
    • Introducing CARV
  • SVM - AI AGENTIC CHAIN
    • Introduction
      • Architecture
      • AI Agent in TEE environment
      • CARV Verifier Nodes
    • Quick Start
      • Bridge Token
      • Explorer
      • Command line tool
      • Reading from CARV SVM Network
      • Writing to the Network
      • Network Info
  • D.A.T.A. - AI FRAMEWORK
    • Introduction
      • DeepSeek Integration
      • D.A.T.A's Core Features
      • How It Empowers AI Agents
      • Driving the Future of AI and Blockchain
      • Leveraging CARV SVM Chain for Privacy and Trustless Data Sharing
    • Quick Start Guide
    • Architecture
    • ERC-7231 (CARV ID)
    • Examples
      • On-Chain Insights
    • Getting Started
      • D.A.T.A Framework Plugin for Eliza
    • Use Cases and Implementation
      • Getting On-Chain Data for AI Agents
      • What's Coming with the D.A.T.A Framework
    • API Documentation
      • News
      • On-chain Data SQL Query
        • Ethereum Schema
        • Bitcoin Schema
        • Base Schema
        • Solana Schema
      • On-chain Data SQL Query by LLM
      • Token Info and Price
      • User Balance by Twitter ID
      • User Balance by Discord ID
  • CARV Ecosystem
    • CARV Play
      • Portal Access
      • Integration Guide
        • .Play Name Service Integration
        • API-Verified Quest (RESTFUL)
        • API-Verified Quest (GraphQL)
        • CARV ID OAuth 2.0
        • CARV ID Telegram SDK
      • Smart Contracts & Security
    • MOFF Bot & Customer Data Platform
    • CARV Account
      • ERC 7231
    • Verifier Nodes
      • How to Purchase Nodes
      • Buyback Program
      • Why Verifier Nodes
      • How do Verifier Nodes Work
        • CARV/veCARV Token
        • CARV Vault
        • CARV NFT License
        • CARV Protocol Service
        • Trusted Execution Environment (TEE)
        • Verifier Node
        • Attestation
        • Delegation
        • Rewards
        • SGX Attestation Verification
      • Verifier Node Sale Dynamics
      • Smart Contract Addresses
      • License Key (NFT)
      • Delegation
      • Node Rewards
      • Join Mainnet Verifier Nodes
        • Prerequisites
        • Delegation Tutorial
        • Operating a Verifier Node
          • Running in VPS
          • Running in CLI
            • Using Source Code
            • Using Docker
            • Gasless Server API
          • Running in Desktop App
      • Explorer
      • FAQ
        • Node Sale
        • Node Operation
  • CARV LABS
    • Introduction
    • Working with CARV Labs
  • Tokenomics
    • Utility
      • veCARV(s)
    • Distribution & Vesting
  • DECENTRALIZED GOVERNANCE
    • ⚔️Universal Guardian Program
    • 📔DAO Governance
    • 🌏Community Programs & Activities
  • Resources
    • 🗜️Writings
    • 🗞️CARV in the News
    • 🫶Social & Community Links
    • 🅰️Brand Guideline
    • 💰Job Openings
Powered by GitBook
On this page
  1. CARV Ecosystem
  2. Verifier Nodes
  3. Join Mainnet Verifier Nodes
  4. Operating a Verifier Node
  5. Running in CLI

Using Source Code

PreviousRunning in CLINextUsing Docker

Last updated 7 months ago

Note that the configuration may change while testing. Please check this page consistently for operation info.

Before you start

The verifier is written in Golang. Before you start, you should make sure you have Golang installed correctly. For more details check: .

Clone the source code

The verifier code is open source and currently in development. You can clone the GitHub repository and build the source: .

git clone https://github.com/carv-protocol/verifier.git && \
cd verifier && \
make build

Run via binary program

After executing make build or make all, the verifier executable file will be compiled into the ./bin directory. You need to switch to the ./bin directory before executing verifier. run

cd bin

If this is your first time running verifier, you need to specify a private key. The private key will sign the verification transaction.

Never expose your main account's private key. Always generate a brand new private key for operating the node, otherwise generate a new one using the `generate-keystore` command below.

The private key can be passed to the verifier through startup parameters, or written into the configuration file.

Through startup parameters

If you already have a brand new private key generated, you can start your node with the command below.

The private key can be any brand new private key. If the key doesn't hold the CARV node license, you need to go to to delegate your license to this new key.

Commission rate can be set between 0-10. 0 means you don't take any commission from delegators. 10 means you take 10% of the rewards from delegators.

# Pass the pre-generated private key in clear text
./verifier -private-key <Your Private Key> -reward-address <Your Reward Address> -commission-rate <Your Commission Rate>

# By specifying keystore
./verifier -keystore-path <Path to keystore file> -keystore-password <keystore password> -reward-address <Your Reward Address> -commission-rate <Your Commission Rate>

In order to facilitate user operation, verifier provides a tool to generate a new keystore, run

./verifier -generate-keystore -keystore-path <path to generate your keystore file>

After running the command, you will be prompted to enter a password for the keystore. After entering the password, the keystore file will be generated in the specified path. And then you can run the verifier with the keystore file path and password before you delegate to the keystore address.

Through configuration file

If you prefer to config your own parameters, including RPC url, private key mode, etc. you can operate your node using config file, check details below:

  1. Set wallet.mode in the configuration file (../configs/config.yaml) to 1,

  2. Write the plain text private key into wallet.private_key,

  3. Write your reward address into wallet.reward_claimer_addr,

  4. Write your commission rate into wallet.commission_rate. Then run

./verifier -conf ../configs/config.yaml 

Configure the path and password of the keystore:

  1. Set wallet.mode in the configuration file (../configs/config.yaml) to 2,

  2. Write the path and password of the keystore file into wallet.keystore_path

  3. Write the keystore password into wallet.keystore_password.

  4. Write your reward address into wallet.reward_claimer_addr,

  5. Write your commission rate into wallet.commission_rate. Then run

./verifier -conf ../configs/config.yaml

Same for Keystore. Before you run the verifier, you must delegate to the keystore address. After the delegation is successful, you can run the verifier again. Delegated address you can get from the terminal after generating the keystore. You can delegate your License through the explorer .

https://go.dev/doc/install
https://github.com/carv-protocol/verifier
https://explorer.carv.io/verifiers
https://explorer.carv.io/verifiers