# Quick Start

## Quick Overview

GEB is a theoretical paradigm that aims to address core issues in current blockchain technology by combining Bitcoin's fundamental design principles with new technological innovations, providing a fresh perspective for the development of intelligent cryptocurrencies. 

### Here are some problems of the current blockchain technology:

* **Energy-Secure Commercial Closed Loop Disruption**: Bitcoin's PoW created a computational power-based value response system forming a complete energy-secure commercial loop. Newer projects switching to PoS disrupt this relationship.
* **Consensus Quantification Without True Decentralization**: Bitcoin's PoW is a computing-based, non-sequential filtering process that achieves true decentralization, while newer blockchains using predetermined voting rules lose this self-organizing feature.
* **Violation of Individual Decentralization Principles**: Bitcoin's UTXO model ensures each transaction unit's independence, while newer blockchains use centralized account models with global state tree structures, abandoning individual decentralization foundations.

### GEB has some key aspects to solve the problems:

#### Four Core Components:

* Individual Model: Based on Bitcoin's UTXO model, where each transaction unit maintains independence and sovereignty without relying on global state
* λ Calculus: A stateless functional transaction model ensuring distributed computation
* Consensus Algorithm: Uses Bitcoin-style Proof of Work for emergent distributed consensus
* Consensus Perception Algorithm: Maps external energy input to value output, maintaining energy conservation

#### Dual-layer Consensus Architecture:

* Mother Consensus: Inherits Bitcoin network's core design for security and stability
* Sub Consensus (Agere Consensus): Path for future intelligent development

#### Innovative Value:

* Strict adherence to conservation of energy principles
* Maintains emergent properties of decentralization
* Achieves true distributed autonomy
* Establishes complete business closed loop

**The GEB paradigm advocates for system designs that maintain energy conservation and decentralization properties while enabling advanced functionality through its dual-layer architecture.**

## Network Configurations

{% tabs %}
{% tab title="GEB Mainnet" %}

<table><thead><tr><th width="231">Parameter</th><th>Value</th></tr></thead><tbody><tr><td>Network name</td><td>GEB Mainnet</td></tr><tr><td>Type</td><td>Mainnet</td></tr><tr><td>Native Asset Symbol</td><td>BTC </td></tr><tr><td>Decimal</td><td>18</td></tr><tr><td>Chain-ID</td><td>11501</td></tr><tr><td>Explorer</td><td><a href="https://scan.geb.network">https://scan.geb.network</a><br><a href="https://web3.okx.com/explorer/geb">https://web3.okx.com/explorer/geb</a></td></tr><tr><td>RPC Endpoint</td><td>https://rpc-mainnet-1.geb.network<br>https://rpc-mainnet-2.geb.network</td></tr><tr><td>WebSocket</td><td><p>wss://rpc-mainnet-1.geb.network </p><p>wss://rpc-mainnet-2.geb.network</p></td></tr><tr><td>Quick Add</td><td><a href="https://chainlist.org/?search=geb">https://chainlist.org/?search=geb</a></td></tr></tbody></table>
{% endtab %}

{% tab title="GEB Signet" %}

<table><thead><tr><th width="231">Parameter</th><th>Value</th></tr></thead><tbody><tr><td>Network name</td><td>GEB Signet</td></tr><tr><td>Type</td><td>Testnet</td></tr><tr><td>Native Asset Symbol</td><td>BTC </td></tr><tr><td>Decimal</td><td>18</td></tr><tr><td>Chain-ID</td><td>11504</td></tr><tr><td>Explorer</td><td><a href="https://scan-signet.geb.network">https://scan-signet.geb.network</a></td></tr><tr><td>RPC Endpoint</td><td><a href="https://signet.geb.network">https://signet.geb.network</a></td></tr><tr><td>WebSocket</td><td>wss://signet.geb.network</td></tr><tr><td>Quick Add</td><td><a href="https://chainlist.org/?search=geb+signet&#x26;testnets=true">https://chainlist.org/?search=geb+signet&#x26;testnets=true</a></td></tr><tr><td>Faucet</td><td><a href="http://faucet-signet.geb.network/">http://faucet-signet.geb.network/</a></td></tr></tbody></table>
{% endtab %}

{% tab title="BEVM Canary Network" %}

<table><thead><tr><th width="231">Parameter</th><th>Value</th></tr></thead><tbody><tr><td>Network name</td><td>BEVM Canary</td></tr><tr><td>Type</td><td>Preliminary Mainnet</td></tr><tr><td>Native Asset Symbol</td><td>BTC </td></tr><tr><td>Decimal</td><td>18</td></tr><tr><td>Chain-ID</td><td>1501</td></tr><tr><td>Explorer</td><td><a href="https://scan-canary.bevm.io/">https://scan-canary.bevm.io/</a></td></tr><tr><td>RPC Endpoint</td><td><a href="https://rpc-canary-1.bevm.io/https://rpc-canary-2.bevm.io/">https://rpc-canary-1.bevm.io/<br>https://rpc-canary-2.bevm.io/</a></td></tr><tr><td>WebSocket</td><td>wss://rpc-canary-1.bevm.io/ws</td></tr><tr><td>Quick Add</td><td><a href="https://chainlist.org/?search=1501&#x26;testnets=false">https://chainlist.org/?search=1501</a></td></tr><tr><td><strong>Special Reminder</strong></td><td><strong>The highest supported Solidity version is 0.8.13.</strong></td></tr></tbody></table>
{% endtab %}
{% endtabs %}

## Development Tools

You can engage in comprehensive interactions with GEB using the ***Ethereum API*** and ***Substrate API***. We have listed some partnership dev tools [here](https://documents.geb.network/evm-development/integrations) for your quick check. GEB employs **the same account system as Ethereum**, and your mnemonic phrase and private key are interchangeable with your Ethereum account. Consequently, you can use **Metamask** or other wallets fully compatible with Ethereum to interact with GEB.&#x20;


---

# 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://documents.geb.network/quick-start.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.