GEB Network

P2P Infrastructure

A live public blockchain network (the renamed BEVM(λ), a Bitcoin-linked EVM chain built on Substrate) whose project describes it as a reality-perceiving complex adaptive system of cooperating 'Agere' subsystems. Accounts are bound to Bitcoin addresses, bitcoin is used as the gas unit, and a reputation-based 'Agere' consensus layer is described in its white paper. The mainnet produces a block about every six seconds and has a public block explorer, but current traffic is very light. This is not Reflexer's GEB stablecoin framework .

Community

Details

License Mixed by repository: the main chain code is GPL-3.0; some forks are Apache-2.0 or MIT; the white paper repository states no licence; Agere-Consensus reports 'other'. The v0.4.3 release says the published source has not been synchronized to the release and provides binaries only
Dev Status 🟢 Active
Dev Status Detail Active (the mainnet produces blocks and has a public explorer; releases are binaries only, the latest v0.4.3 of December 2025, and the main repository's source history stops in January 2025; traffic is currently very light)
Owner Not stated by the project.
Governing Body Not stated by the project.
Country Not stated by the project.
Stack Rust (Substrate / Polkadot SDK fork with an EVM layer from Frontier); Blockscout explorer; Solidity contracts; Docker images for validator and sync nodes (x86_64)
Funding Not stated by the project.
Last Investigated Nov 12, 2026

Topology view

This tool in the centre and the things it is directly related to. Each line names the kind of relationship.

Topology view: GEB NetworkThis tool in the centre and the things it is directly related to. Each line names the kind of relationship.GEB NetworkBitcoin (Bridges to)BitcoinPolkadot (Built on)Polkadot

Open in Graph Explorer

Affordances

Self-hostable

P2P Infrastructure Attributes

Origins Ecosystem/SDK: a chain lineage that began as a Bitcoin layer-2 exploration (Taproot Consensus, SuperBitcoin, BitAgere, BEVM(λ)) and was renamed GEB, after Gödel, Escher, Bach
Database Distributed (consensus-based): a Substrate chain with an EVM layer, archive and pruned node modes
Data Formats EVM transactions and contracts; Substrate extrinsics; Bitcoin OP_RETURN commitments for entry
Mobile Support Not stated by the project.
Web Support Yes: a public block explorer and a Polkadot-style wallet front end
Native Apps Not stated by the project.
Terms Self-hosting: run a validator, sync or archive node from the published binaries or Docker images
Funds Not stated by the project.
Based On Bitcoin (account binding and entry), Substrate / Polkadot SDK (forked from ChainX), the Frontier EVM layer, an 'Agere' reputation consensus described in the white paper
P2P Architecture Public blockchain with validators that evaluate competing candidates under a reputation-convergence layer (Agere0) as the white paper describes it; the consensus algorithm in the code is not named
Overlay Network Global
Content Addressing No
Local-First N/A
E2EE No: a public ledger; transaction contents are visible
Byzantine Fault Tolerance Not stated by the project.
Signature Signature (Substrate and Ethereum-style keys; a Bitcoin-linked account binding); the scheme is not named
Permissions Not stated by the project.
Protocol Maturity / Standardization Project specification and white paper; not submitted to a standards body
Infrastructure Function Smart-contract execution with bitcoin as the gas unit, and an EVM rent-burn mechanism effective 2026-01-01 per the v0.4.3 release notes
Threat Model Not stated by the project in the pages read.
Volunteer / Node Model Not stated by the project (validator, sync and non-tracing node images are published; the validator set is not listed)
Traffic Visibility No content hiding: a public ledger.
Active Deployment Scale The mainnet explorer on 2026-11-12 showed about 14.06 million blocks, a block time of about six seconds, 960,303 addresses and 7.27 million transactions, and 28 transactions so far that day (an incomplete day)

Relationships

How this tool connects to other tools and organizations, from relationships reviewed by the OpenHaven data steward. They describe how projects connect, not how good they are.

Bridges to
Built on