search
Ctrlk

Overview

Introduction

ISHTA (Inflation Stabilized Hybrid Token Architecture) is a next-generation Proof-of-Stake (PoS) consensus mechanism designed to address the volatility and instability inherent in traditional PoS reward systems. It introduces a novel inflation curve alongside a layered security architecture leveraging Confidential Compute and Threshold Encryption to ensure robustness, scalability, and data integrity. This document details the architectural components, core concepts, and security mechanisms underpinning the ISHTA protocol.

High-Level System Diagram:

Key Architectural Principles:

  • Hybrid Inflation Curve: ISHTA employs a dynamic inflation curve with two phases: initial growth and stabilization. The initial phase sees a moderate inflation to incentivize early adoption. The stabilization phase uses a decreasing inflation rate, governed by network activity (transaction volume, staking ratio), aiming for a low and predictable inflation rate. Formula Example: InflationRate = BaseRate * (1 - (StakingRatio * StabilityFactor))

  • Layered Security: Defense in depth is achieved through combining Confidential Compute, Threshold Encryption, and a robust data availability solution.

  • Decentralized Governance: The Guardian manages protocol parameters through on-chain voting, ensuring community participation.

  • Scalability: The system utilizes techniques like data sharding and efficient consensus algorithms to handle high transaction throughput.

Components Overview:

  • Stakers: Token holders delegate tokens to Validators, earning rewards proportional to their stake and Validator performance. Delegation is handled through smart contracts.

  • Validators: Nodes responsible for validating transactions, creating blocks, and participating in consensus. Validators run within secure enclaves (Section 2.3). They are rewarded with transaction fees and staking rewards.

  • Guardian: Elected committee managing protocol parameters. Parameter changes require a majority vote. The Guardian also handles emergency situations.

  • Confidential Compute Enclave: Secure environments (e.g., Intel SGX) protecting sensitive data and execution.

  • Data Availability Layer: Ensuring transaction data is accessible for verification. (e.g., using KZG commitments – see below).

Last updated