Use the network
A safer way to explore on-chain applications.
- Create a wallet with Boing Express
- Get testnet BOING from the faucet
- Send and receive
- Explore accounts, blocks and transactions in Boing Observer
- Connect to applications
Public testnet — mainnet not live
Quality, enforced by the protocol.
Boing Network — the quality-assured Layer 1
Boing is an independent Layer 1 built from first principles, with transparent deployment checks and open participation for users, developers and validators.
- Public testnet and faucet
- Purpose-built VM, not EVM-compatible
- ~2-second target block time under load
- Open validator and node participation
Blockchains make it easy to deploy. Boing adds a quality gate.
The Boing Quality Gate screens deployments against transparent rules before they reach the ledger. Automated checks handle clear cases; a decentralized community pool reviews edge cases.
What it is
Boing introduces protocol-level deployment checks designed to identify and restrict deployments that fail transparent quality criteria before they are accepted on-chain.
What it is designed to do
Designed to reduce malicious, deceptive and low-quality deployments through transparent, protocol-level checks. The rules are public, and outcomes remain visible.
What it does not claim
No gate can prevent every kind of abuse. The Quality Gate reduces risk and makes decisions auditable; it does not replace your own review of an application. Read the QA design (PDF).
How the Quality Gate works
Five steps from submission to a public, auditable outcome.
- 1
Deployment submitted
A developer submits contract bytecode with a declared purpose.
- 2
Automated checks evaluate it
Transparent rules cover bytecode, size, opcodes and declared purpose.
- 3
Clear cases are decided by the protocol
Deployments that clearly meet or clearly fail the rules are accepted or rejected, with the rule that applied.
- 4
Edge cases go to the community pool
When the rules cannot decide, a decentralized pool of reviewers does.
- 5
Outcomes remain visible and auditable
Decisions are observable in Boing Observer, not hidden in a private process.
Built from first principles
An independent chain with its own stack, not a fork or an EVM-compatibility layer.
RustProtocol and node implementation
HotStuff PoSProof-of-stake consensus
Ed25519Signatures
BLAKE3Hashing
Purpose-built VMNot EVM-compatible
~2 s blocksTarget block time when transactions are pending
Secure by design
Rust, HotStuff proof of stake, Ed25519 and BLAKE3.
Open participation
Permissionless for users, developers and validators.
Transparent by default
Observable rules, deployments and outcomes.
Built for real applications
Native accounts, adaptive gas and cross-chain liquidity.
Choose your role
Start where you are. Everything below runs on the public testnet.
Build an application
Build on an independent chain with native account and application primitives.
- JSON-RPC and the Boing SDK
- Purpose-built VM
- Native account abstraction, session keys and social recovery
- Adaptive gas
- Deployment QA requirements
- Clear testnet docs
Run a node
Help operate an open network with transparent participation rules.
- Rust node with HotStuff consensus
- Public testnet and node setup guides
- Validator registration
- Slashing and appeals rules
- Launch-partner pathway
- Mainnet readiness milestones
For institutions: Boing is designed for verifiability and institutional review, with transparent, rule-based infrastructure for applications that require verifiable deployment standards. Audits, genesis, incident response and mainnet readiness are still open items; see the roadmap below.
Honest roadmap
Testnet status is a strength: here is what exists, what is being built, and what must be true before mainnet.
Live on testnet
- Public testnet RPC and faucet
- Quality Gate deployment checks, with a published rule registry
- Boing Express wallet (web and Chrome extension)
- Boing Observer explorer, including QA visibility
- Node, CLI and SDK tooling
In development
- Community review pool for edge cases
- Validator set growth and production hardening
- Cross-chain liquidity routes in Boing Finance
- Incentivized testnet (not currently running)
Required before mainnet
- Independent security audits
- Genesis and launch-partner validator readiness
- Finalized slashing and appeals process
- Incident-response process
- Published mainnet readiness milestones met
Not yet complete
- Mainnet: not live
- Independent audits: not complete
- Institutional review materials
The Boing ecosystem
Four products, one network. Start on the public testnet in three steps.
- 1. Get a walletCreate a Boing Express wallet (web or Chrome extension).
- 2. Get testnet BOINGRequest free testnet BOING for fees.
- 3. Send and verifySend your first transaction, then find it in Boing Observer.
Boing Network
The quality-assured Layer 1
The core protocol and ecosystem: docs, faucet, node setup and the Quality Gate.
Public testnetBoing Express
Your gateway to Boing
A non-custodial wallet designed for the Boing ecosystem, for the web and Chrome.
Public testnetBoing Observer
See what happens on-chain
An explorer with integrated QA transparency: blocks, transactions, accounts and Quality Gate decisions.
Public testnetBoing Finance
Move liquidity across chains
A cross-chain liquidity interface spanning Boing and external networks.
EvolvingTokenomics
Sustainable value design — uncapped total supply with a set initial supply at mainnet launch. When circulating supply reaches the floor, new waves are minted to rebalance.
UncappedTotal Supply
Set at launchInitial Supply
~2sTarget Block Time (when transactions are pending)
Initial Supply Allocation
How the fixed initial supply (at mainnet launch) is allocated. Staking rewards are topped up by new waves when supply reaches the floor, so the initial allocation leans more toward treasury and community.
- Staking Rewards 55%
- Treasury 30%
- Community & Grants 15%
Total supply is uncapped. Initial supply is fixed at mainnet launch; new waves mint when circulating supply reaches the floor.
Fee Allocation
- Validators 80%
- Treasury 20%
Emission Schedule
Usage ↑ → Fees ↑ → Validators & Treasury ↑ → Security & Ecosystem ↑ → Value ↑
Built for real applications
Native accounts, adaptive gas and cross-chain liquidity as supporting capabilities.
Native Account Abstraction
Gasless txs, social recovery, session keys — built into the protocol.
Adaptive Gas Model
Dynamic gas that responds to network conditions with predictable caps.
Cross-chain liquidity
Protocol-level primitives for liquidity routing across chains.
Transparent Slashing
Auditable slashing conditions and appeal mechanisms.