HbarSuite Docs
  • Welcome to HbarSuite
  • HbarSuite Developer Documentation
    • HbarSuite Smart Engine Applications
      • @hsuite/cross-chain-exchange
      • @hsuite/dao
      • @hsuite/exchange
      • @hsuite/launchpad
      • @hsuite/multisig
      • @hsuite/nft-exchange
    • HSuite Libraries
      • @hsuite/api-key
      • @hsuite/auth-types
      • @hsuite/auth
      • @hsuite/client-types
      • @hsuite/client
      • @hsuite/dkg-types
      • @hsuite/hashgraph-types
      • @hsuite/health
      • @hsuite/helpers
      • @hsuite/ipfs
      • @hsuite/smart-config
      • @hsuite/smart-network-types
      • @hsuite/smart-transaction-types
      • @hsuite/smartnode-sdk
      • @hsuite/snapshots
      • @hsuite/subscriptions-types
      • @hsuite/subscriptions
      • @hsuite/throttler-types
      • @hsuite/throttler
      • @hsuite/users-types
      • @hsuite/users
      • @hsuite/validators-types
  • General Documentation
    • Tokenomics
      • Tokenomics v1
      • Tokenomics V2
    • Smart Apps and Interaction
      • Subscription-Based Model
      • Token-Gate Model
    • The Smart Node Network
      • security-layer
        • Security Layer Integration
        • Setting Up Secure Clusters
        • Generating and Sharing Keys Collaboratively
        • Protecting Secrets with Shamir's Method
        • Managing Cluster Membership
        • Handling Node Expulsion and Replacement
        • Automating Responses to Network Changes & Key Rotation
        • Ensuring Continuous Operation and Recovery
      • Understanding Validators in Our System
        • Type of Validators Explained
    • What is a Smart Node?
  • Restful APIs Documentation
Powered by GitBook
On this page
  • Consensus Validators
  • Token Validators
  • Account Validators
  • Adding and managing Validators
  • Why Validators Matter
  1. General Documentation
  2. The Smart Node Network
  3. Understanding Validators in Our System

Type of Validators Explained

Here there are some examples of types of validators:

Consensus Validators

Purpose: Ensure that decisions or agreements within the network are properly authorized and executed.

Example: Verifying that a DAO proposal meets all criteria before it's accepted by the network.

Token Validators

Purpose: Manage and verify transactions related to tokens.

Example: Checking the validity of a new token mint request or ensuring that token transfers are legitimate.

Account Validators

Purpose: Oversee transactions involving user accounts to ensure security and accuracy.

Example: Validating the creation of a new account or confirming the authenticity of a token transfer between accounts.

Adding and managing Validators

Our system is designed to be flexible and scalable. This means that as new types of transactions emerge or as the network grows, new validators can be added seamlessly. This adaptability ensures that the Validators Service can handle evolving requirements without compromising on security or efficiency.

Why Validators Matter

  • Security: Prevent unauthorized or malicious transactions that could harm the system.

  • Accuracy: Ensure that all transactions are correct and follow the defined rules.

  • Reliability: Maintain the trustworthiness and smooth operation of the network by consistently verifying transactions.

  • Scalability: Adapts to growing and changing needs by adding new validators as necessary.


Built with ❤️ by the HbarSuite Team Copyright © 2024 HbarSuite. All rights reserved.

PreviousUnderstanding Validators in Our SystemNextWhat is a Smart Node?

Last updated 3 months ago

[//]: # (Diagram showing four quadrants: Scalability, Security, Reliability, and Accuracy with their respective icons and descriptions)