Gauss Docs
  • 🌐Getting Started
    • Welcome to Gauss
    • Whitepaper
      • Blockchain Providers Need to Do Better
        • Solving a Lack of Token Adoption
          • An Evolving Space With Untapped Potential
        • Security & Reliability
          • Curation & Vetting
            • Important Note For Brands
        • Token Creation
      • WHY BUILD WITH GAUSS?
      • Use Cases
        • Use Cases (Chart)
      • Roadmap
      • Technical Background and Blockchain Development
        • Why Another Blockchain?
        • Gauss 1.0: Built With Efficiency and a Strong Infrastructure to Launch Rapidly
        • Gauss 2.0: Added Functionality For a Better User Experiance
          • Noble Swap 2.0
          • NFTs in Gauss 2.0
          • Token Development Kit (TDK)
          • Gaming DAO
          • Omnipool
      • Token Economics
        • Gang Token Economics: Designed to Ensure Trust and Transparency
        • Token Locking Schedule
        • Reflections: Rewarding the Gauss Community
        • Charitable Allocations: Grants, Scholarships, & Financial Assistance
      • The Gauss Team
      • Important Definitions
      • DISCLAIMER
        • PURCHASER WARNING
        • PROMINENT STATEMENTS
        • FUTURE STATEMENTS
        • VALUE RISKS
        • NOT A SECURITY
    • How To Connect
      • Create Metamask Wallet
    • Links
  • ⚡Launching with Gauss
    • Benefits of Building with Gauss
      • Fostering an Environment for Success
      • Gauss Growth Grant Program
      • Gauss Liquidity Program
      • Ecosystem Integrity Fund
      • Client Referral Program
    • A Guide to Curation
      • Core Principles and Curation Guidelines
      • Curation Stages and Processing Fees
    • Building on Gauss
  • 🖥️Gauss Ecosystem
    • Gauss Chain
      • Polygon-Edge Overview
      • Architecture
      • Consensus
      • Client Modules
        • Blockchain
        • Minimal
        • Networking
        • State
        • TxPool
        • JSON RPC
        • Consensus
        • Storage
        • Types
        • Syncer
        • Sealer
        • Other Modules
      • Polygon-Edge Performance Reports
      • For Developers
        • Operate a Node
          • Local Install
          • Genesis Contract
          • Server Config
          • CLI Commands
          • Key Management
        • Run a Validator
          • Validator FAQ
        • Smart Contract Deployment Permissioning
        • Deploying Contracts
          • Remix
          • Truffle
          • Hardhat
          • Replit
    • Gauss Explorer
      • Features
      • Navigating the Explorer
        • Menus
        • Blocks
        • Transactions
      • Verifying a Smart Contract
        • Hardhat Plugin
        • Sourcify Plugin
        • OpenZeppelin Plugin
      • Interacting With Smart Contracts
      • Exporting Transactions
      • FAQ
      • For Developers
        • Gauss Explorer Dependencies
        • Deployment Guide
          • Smart Contract Verification
          • Cleaning an instance from the previous deployment
          • ENV Variables
          • Testing
        • APIs
          • Requests & Limits
          • GraphQL
          • ETH RPC
    • Noble Swap
      • Liquidity Boost Program
    • Tokens
    • Gauss NFTs
      • Ferro Cards
      • F.E.R.R.E.T. NFTs
    • Contests & Giveaways
    • Gauss Faucet
      • For Developers
    • Address List
  • 💡Additional Resources
    • Partnerships & Affiliates
    • Discord Channel
    • Contact Us
    • Learning Materials
      • Web3 Glossary
    • Media Kit
Powered by GitBook
On this page
  1. Getting Started
  2. Whitepaper
  3. Technical Background and Blockchain Development

Gauss 1.0: Built With Efficiency and a Strong Infrastructure to Launch Rapidly

PreviousWhy Another Blockchain?NextGauss 2.0: Added Functionality For a Better User Experiance

Last updated 2 years ago

The Gauss Ecosystem 1.0 is built on a permissioned, EVM-compatible blockchain. We are utilizing the IBFT 2.0 consensus algorithm, a Proof of Authority (PoA) protocol. PoA protocols are a type of Proof of Stake (PoS) protocol. They give the ecosystem authority to permit or deny validator nodes and prevent unapproved smart contract deployment. Each node will be owned and operated by Gauss and our highly-trusted partners. Only these trusted nodes are “validators.” Each node in the pool takes turns voting to add or remove blocks, while the other nodes sign the new block to validate it.

IBFT is designed to be an enterprise-ready solution. These models offer immediate finality. Meaning there are no forks, and all valid blocks get included in the chain. This is one of the more secure blockchain options. It requires control over two-thirds of the validator pool to change, add, delete, or otherwise . It also allows for a permissioned network, with granular permissions based on an account or node. These permissions allow us to prevent absolutely anyone from deploying smart contracts unless they are pre-approved, eliminating potential bad actors from our ecosystem.

Building upon our blockchain, we launched a blockchain explorer to provide a place for users to follow transactions in real-time, creating a necessary level of transparency for our community. We are also launching . This is a native token swap that allows users to exchange and stake any tokens in the Gauss Ecosystem. Noble Swap has a built-in NFT marketplace, so users can mint and trade all forms of NFTs.

🌐
corrupt data
Noble Swap
Gauss Ecosystem