Skip to main content

About Boing Network

Authentic. Decentralized. Optimal. Quality-Assured. — six pillars: Security, Scalability, Decentralization, Authenticity, Transparency, True QA.

Six pillars

1. Security

Safety and correctness over speed. BFT consensus (HotStuff), Ed25519 + BLAKE3, RPC rate limiting, equivocation detection. Security advisories and incident response per SECURITY-STANDARDS.

2. Scalability

High throughput without compromising other pillars. Parallel transfers, conflict-free scheduling, gas metering. Typical block time ~2 seconds; access-list batching enables parallel execution.

3. Decentralization

Permissionless participation. No whitelist; anyone with stake can validate. P2P (libp2p), bootnodes, DHT (roadmap). No central gatekeeper for consensus, governance, or QA.

4. Authenticity

Unique architecture and identity. Custom VM (stack-based, Boing opcodes), HotStuff BFT consensus, BLAKE3 + Ed25519, independent L1 — not a fork or framework.

5. Transparency

100% openness. Open source, public specs, account proof APIs, human-readable signing. QA rejections include rule_id and message for structured feedback. The explorer publishes a live QA transparency dashboard (pool queue and governance parameters from public RPC).

6. True quality assurance

Protocol-enforced QA: only assets meeting rules and security bar are allowed. Meme leniency; no malice. Every deployment is classified as allow, reject, or unsure. Unsure cases are routed to the community QA pool for review. Opcode whitelist, well-formedness, blocklist, scam patterns, and purpose declaration are part of the check. See Quality assurance rules and guidance for the current policy and canonical malice definition. See live pool status on QA transparency and machine-readable details in RPC-API-SPEC.

This explorer

Search by height, 64-character hex (tx id, block hash, or account), or use Tools. Home