# THE GTBS NETWORK ARCHITECTURE

### Decentralized Network

GTBS operates a decentralized multi-layer network:

* Layer 1 — GTBS Chain (Mainnet)
* Layer 2 (future) — Rollups & sidechains
* Layer 3 — App-level clusters for gaming, OTT, NFTs\
  \
  Every node validates cryptographically signed transactions, maintains consensus, and contributes to block production.

### DPoS Consensus Mechanism

**DPoS (Delegated Proof of Stake)** is a blockchain consensus algorithm where network users vote to elect delegates (also called witnesses or block producers) who are then responsible for validating ransactions and creating new blocks. \
\
This approach improves on traditional Proof of Stake by increasing scalability and transaction speed, as a smaller, elected group of validators handles block production. The system relies on user participation to vote for these delegates, who then share rewards with their voters.

GTBS uses Delegated Proof of Stake, optimized for:

* High transaction throughput
* Fast finality (5 seconds)
* Low energy consumption
* Democratic staking participation

#### **How it works**

* **Voting**: Users stake their tokens to vote for delegates they trust. They can vote directly or delegate their voting power to another entity.
* **Delegation**: The delegates with the most votes are elected as the active witnesses or block producers.
* **Block production**: These elected delegates are responsible for verifying transactions and creating new blocks in the blockchain.
* **Rewards**: When a delegate successfully produces a block, they receive a reward, which is typically shared with the users who voted for them.
* **Accountability**: Delegates who fail to perform their duties (like missing a block) are not rewarded and risk losing votes from the community. 

<figure><img src="https://752533933-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzaqSxfrTfPXvMnYyQ0B5%2Fuploads%2FaxahXqaNpSKCGt9nKzsZ%2Fdpos.png?alt=media&#x26;token=c07c6218-8a1e-422f-a7b5-71dc94cee52a" alt=""><figcaption></figcaption></figure>

#### Key Characteristics:

* 20 active validators
* 20 delegates
* Weighted-voting through stake
* Slashing for poor performance
* Automatic validator rotation
* Delegator staking yields proportional rewards<br>

### Resources on GTBS

The GTBS resource framework enables predictable performance and stable dApp execution.

Resources include:

#### Compute Units (CU)

Execution power allocated for smart contracts.

#### Network Units (NU)

Bandwidth & transmission resource.

#### Storage Units (SU)

Persistent chain-level storage for state and contracts.

GTBS ensures deterministic execution—resources are allocated proportionally based on staked GTBS Coin.

### Decentralized Identities (DeID)

GTBS introduces GTBS DeID, a decentralized identity layer enabling:

* Wallet-bound identity
* KYC-linked identity (optional)
* DID-based login
* NFT-linked identities
* Identity for dApps, creators, OTT accounts, cloud accounts<br>

Users maintain full control over their identity without relying on centralized servers.

### Transactions Per Second (TPS)

GTBS is optimized for high throughput.

* Baseline TPS: 8,000–12,000
* Peak TPS: Up to 25,000 with batching
* Block size: Dynamic
* Latency: \~2 seconds
* Finality: 5 seconds<br>

### Block Production

Blocks are produced every 5 seconds.

#### Per-block minting:

* 9.5129 GTBS minted per block
* Resulting in 164,383.56 GTBS/day<br>

### Block Producers

Block producers = Active validators.

Roles:

* Validate transactions
* Run consensus
* Propose new blocks
* Secure the chain
* Participate in governance<br>

### Decentralized Governance Model

GTBS uses a decentralized, transparent governance model:

Stakeholders include:

* Validators
* Delegators
* NFT holders
* Ecosystem partners
* Token holders

Governance covers:

* Software upgrades
* Parameter changes
* Validator additions
* Ecosystem funding
* Treasury use
* Voting weights are stake-based.

### GTBS Consortium Structure

GTBS’s consortium includes:

* GTBS Core Team
* Independent validators
* Technical partners
* Ecosystem builders
* Community representatives<br>

This ensures:

* No single-point control
* Transparency
* Continued decentralization<br>

### GTBS Signing Request (GSR)

GSR is GTBS’s version of a signing request protocol similar to XPR’s PSR.

GSR enables:

* Wallet-to-dApp authorization
* MultiVM transaction signing
* Seamless login
* Secure smart contract interactions
* Off-chain signing compatible with Web3 wallets<br>

GSR standardizes interactions across:

* Mobile wallets
* Browsers
* Exchanges
* Cloud services<br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://gatbits-gtbs-chain.gitbook.io/gatbits-gtbs-chain-docs/documentation/basics/the-gtbs-network-architecture.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.