No new magic. Proven parts.
MoonBite didn't invent a new consensus mechanism, and it won't pretend to. It stands on things that already work โ Bitcoin's double-spend solution, Litecoin's battle-tested codebase, and Monero's CPU-friendly RandomX proof-of-work โ and sets its own parameters on top. This page lays out those choices in plain terms.
What MoonBite inherits
Good engineering builds on what works. MoonBite doesn't reinvent two problems that are already solved.
Where MoonBite makes its own calls
These are the specific decisions that set MoonBite apart from its parent chains.
2-minute block target
A new block is targeted every 120 seconds โ five times faster than Bitcoin โ so you wait less for a first confirmation. Difficulty retargets every 60 blocks (about two hours), moving at most 4x per step, to hold that target as hash rate rises and falls.
10 MBITE genesis reward
The launch block subsidy is 10 MBITE, paid entirely to the miner who solves the block. No founder reward, no pre-allocated treasury, no developer cut. Every coin issued is miner pay.
Halving every 1,650,000 blocks
Every 1,650,000 blocks (~6.27 years at the 2-minute target), the subsidy is cut in half. Same halving mechanism as Bitcoin, on a block-count schedule matched to MoonBite's block time.
Cap: just under 33,000,000 MBITE
Total supply is bounded. Each halving cuts the rate of new issuance in half, and the sum of every halving converges to a finite limit just under 33 million MBITE. No coins can be created outside this schedule.
No premine โ fair launch
Not one MBITE existed before public mining began. The founders hold no special allocation. Every coin was earned through open, competitive proof-of-work. Any early mining by the team was disclosed in the open under ADR-006.
Bech32 address format
MoonBite uses bech32-encoded addresses for all standard outputs. Mainnet addresses start with moon1; testnet addresses start with tmoon1. A built-in checksum catches most copy-paste slips before a transaction ever goes out.
At a glance
moon1... (bech32)tmoon1... (bech32)Why we chose what we chose
Why build on Litecoin's codebase?
Litecoin is one of the oldest continuously running blockchain codebases in the world. Its consensus rules are battle-tested, and its security model is well understood after more than a decade of adversarial pressure. Starting from a proven base means fewer chances for fresh implementation bugs. MoonBite layers its own proof-of-work (RandomX), parameters, and address format on top instead of rewriting everything from scratch.
Why RandomX over SHA-256 or scrypt?
SHA-256 mining is run almost entirely by ASICs from a handful of companies, and mature scrypt ASICs dominate Litecoin. RandomX goes further than either: it is designed so a general-purpose CPU is the best hardware, permanently. GPUs gain little and no viable ASIC exists โ Monero has proven the design under real adversarial pressure since 2019. That keeps the mining base spread across ordinary people's computers instead of consolidating into farms.
Why a lower supply cap?
MoonBite's cap of roughly 33 million โ not Bitcoin's 21 million โ falls out of the 10-MBITE genesis reward and the 1,650,000-block halving schedule. It wasn't picked arbitrarily; it's the direct result of designing the emission curve around a specific block time and halving period. The math is open and checkable in the source code.
Why no premine?
A premine โ founders minting coins before the public can โ is the most common source of hidden conflicts of interest in crypto. Cutting it entirely means every MBITE was earned through publicly verifiable work. It also means the founders can't quietly dump a big stash on a future market. The fair-launch design is written up in ADR-006.
The code is the spec
There's no separate academic PDF here. The running software is the specification. Every parameter on this page is enforced in the node code, in plain sight for anyone who wants to audit it.