Blockchain

Quelle · Layer-1 technical annex

Quelle is a sovereign Layer-1. This page is the technical annex for operators and builders. The brand story remains the Litepaper and White Paper — here we document how the network presents itself on the wire.

Network identity

QueChain is the public deployment face of Quelle under quechain.network. Addresses use Bech32 prefix quelle. The native coin is QUE, base denomination uque, six decimals. That identity is stable: it is how wallets, validators, and contracts speak the same language.

Native coin QUE
Base denom uque (6 decimals)
Bech32 prefix quelle
Reward program QUT — see Economy
Public focus MVP testnet execution · Mainnet genesis blueprint prepared

Public endpoints

Canonical hostnames for the live network. Confirm operational status on status.quechain.network.

Service URL Role
RPC https://rpc.quechain.network Node status, queries, broadcast paths
LCD / REST https://lcd.quechain.network REST module queries
gRPC grpc.quechain.network High-performance client access
Platform API https://api.quechain.network Product services beside the ledger
Faucet https://faucet.quechain.network Testnet distribution
Explorer https://explorer.quechain.network Human-readable chain views

Implementation stack

The Quelle chain is implemented with the Cosmos SDK, CometBFT consensus, and CosmWasm smart contracts. These are engineering choices that give us modularity and a proven operator ecosystem. They appear on this page because this is the technical annex. On stage and in brand materials, we present Quelle — the AI-native Layer-1 — not a toolkit brochure.

On-chain and platform responsibilities

QUE balances, staking, fees, and globally agreed contract state settle on-chain. Product profiles, PoWd scoring detail, and QUT program ledgers run as platform services keyed to QID, with settlement pathways where the protocol requires them. Clean boundaries keep the brand honest: the Layer-1 is the Layer-1.

Client security baseline

User seeds never transit Quelle backends. Clients sign locally. Prefer canonical hostnames. Treat any request for a recovery phrase as hostile.