HbarSuite Docs
  • Welcome to HbarSuite
  • HbarSuite Developer Documentation
    • HbarSuite Smart Engine Applications
      • @hsuite/cross-chain-exchange
      • @hsuite/dao
        • DAO Application Testing
      • @hsuite/exchange
      • @hsuite/launchpad
      • @hsuite/multisig
      • @hsuite/nft-exchange
      • HSuite Smart App - Enterprise Hedera Application Framework
    • HSuite Libraries
      • @hsuite/api-key - Enterprise API Key Authentication System
      • @hsuite/auth-types
      • @hsuite/auth - Authentication Module
      • @hsuite/client-types
      • @hsuite/client - Client Service Module
      • @hsuite/dkg-types - Distributed Key Generation Type Definitions
      • @hsuite/hashgraph-types - Hedera Hashgraph Type Definitions
      • @hsuite/health - Comprehensive System Health Monitoring
      • @hsuite/helpers - Utility Library
      • @hsuite/ipfs - InterPlanetary File System Integration
      • @hsuite/shared-types - Shared Type Definitions
      • @hsuite/smart-config - Configuration Management
      • @hsuite/smart-ledgers - Multi-Ledger Management
      • @hsuite/smart-network-types - Smart Network Type Definitions
      • @hsuite/smart-transaction-types - Smart Transaction Type Definitions
      • @hsuite/smartnode-sdk - SmartNode Software Development Kit
      • @hsuite/snapshots - Multi-Ledger Token Snapshot Management
      • @hsuite/subscriptions-types - Subscription Management Type Definitions
      • @hsuite/subscriptions - Enterprise Subscription Management System
      • @hsuite/throttler-types - Rate Limiting Type Definitions
      • @hsuite/throttler - Advanced Rate Limiting for NestJS
      • @hsuite/users-types - User Type Definitions
      • @hsuite/users - User Management Module
      • @hsuite/validators-types
  • General Documentation
    • Smart Apps and Interaction
      • Subscription-Based Model
      • Token-Gate Model
    • The Smart Node Network
      • security-layer
      • Type of Validators Explained
      • Understanding Validators in Our System
      • Automating Responses to Network Changes & Key Rotation
      • Ensuring Continuous Operation and Recovery
      • Generating and Sharing Keys Collaboratively
      • Handling Node Expulsion and Replacement
      • Managing Cluster Membership
      • Protecting Secrets with Shamir's Method
      • Security Layer Integration
      • Setting Up Secure Clusters
    • Tokenomics
      • Tokenomics v1
      • Tokenomics V2
    • What is a Smart Node?
  • Restful APIs Documentation
Powered by GitBook
On this page
  • What are Validators?
  • How do Validators work?
  • 1. Identifying the Transaction Type
  • 2. Selecting the Appropriate Validator
  • 3. Validating the Transaction
  • 4. Finalizing the Transaction
  1. General Documentation
  2. The Smart Node Network

Understanding Validators in Our System

PreviousType of Validators ExplainedNextAutomating Responses to Network Changes & Key Rotation

Last updated 4 months ago

In our system, Validators play a vital role in ensuring that all transactions are secure, accurate, and adhere to the established rules. Think of them as the gatekeepers that oversee and verify every action within our network to maintain its integrity and reliability, all written on the Hashgraph Consensus Service (HCS).

What are Validators?

Validators are specialized components that review and confirm transactions before they are processed. They ensure that each transaction meets the necessary criteria and follows the correct procedures. By doing so, validators help prevent errors, unauthorized actions, and maintain the overall health of the system.

How do Validators work?

Our Validators Service manages different types of validators based on the nature of each transaction. Here's a simplified overview of how it operates:

1. Identifying the Transaction Type

When a transaction is initiated, the Validators Service first determines its type. Transaction types can vary, such as:

  • Consensus Transactions: Involve agreements or decisions within the network.

  • Token Transactions: Related to the creation, updating, or management of tokens.

  • Account Transactions: Pertaining to user accounts, like creating a new account or transferring funds.

2. Selecting the Appropriate Validator

Based on the identified transaction type, the Validators Service selects the corresponding validator. Each validator is specialized to handle specific kinds of transactions, ensuring that each one is reviewed accurately.

3. Validating the Transaction

Once the appropriate validator is selected, it thoroughly checks the transaction. This includes verifying details, ensuring compliance with rules, and confirming that all necessary information is present and correct.

4. Finalizing the Transaction

After successful validation, the transaction is approved and processed. If any issues are detected during validation, the transaction is flagged for further review or rejected to maintain system integrity.


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

Transaction Types