Open the hood.
No magic here. MoonBite is a set of open rules, and every participant enforces them independently. Here's what's really happening when you mine, send, or check a transaction.
Mining: electricity into trust
Proof-of-work is how total strangers agree on one shared history without ever trusting each other.
What miners actually do
A miner hashes a candidate block header over and over, nudging a nonce each time, until the result drops below a network-set target. Finding a valid hash takes real computation — you can't fake it, you can't shortcut it. The first to land a valid solution broadcasts the block and takes the reward.
Why RandomX?
MoonBite uses RandomX — the CPU-optimized algorithm that has secured Monero since 2019. RandomX executes randomly generated programs against a large in-memory dataset, which is exactly what general-purpose CPUs are good at and exactly what fixed-function ASICs are bad at. The result: ordinary computers stay competitive, and no mining monopoly can buy its way in.
Difficulty adjustment
The network retunes the target difficulty on its own, so blocks keep arriving at about the right pace whether miners pile in or drop out. MoonBite aims for one new block every 120 seconds — 2 minutes — and re-tunes difficulty every 60 blocks (about two hours), never moving it more than 4x in one step.
What makes it secure
To rewrite a past transaction, an attacker has to redo every bit of proof-of-work from that point on — and outrun the honest network still stacking blocks on top. The more hash rate the network has, the more that attack costs.
Blocks & the blockchain
Every block is a permanent, ordered record chained to every block before it.
A block is a batch
A block bundles transactions waiting in the mempool, a hash pointing back at the previous block, and proof that real mining work was done. Miners pick which transactions go in — usually the ones paying higher fees.
Chaining creates permanence
Each block carries the hash of the one before it. Change a single thing in block 1,000 and you break the hash block 1,001 expects — then 1,002, then every block after. That chain of proof-of-work makes tampering obvious, with no central authority policing it.
Confirmations & finality
Once your transaction lands in a block, every block mined on top is another confirmation. More confirmations, more cumulative work an attacker would have to burn to undo it. For most purposes, 6 confirmations (~15 minutes) is as good as final.
Coins controlled by cryptography
The MoonBite network has no accounts. Just keys and addresses.
Private key
A private key is a huge random number, generated on your device. It's the only proof you own the coins at your address. Anyone holding it can spend them; without it, nobody can — not even MoonBite's developers. Guard it like it's everything, because it is.
Address (public)
Your address comes from your private key through one-way cryptography. Share it freely — it's just a destination, nothing more. MoonBite mainnet addresses start with moon1 (bech32); testnet with tmoon1.
Signing a transaction
When you send MBITE, your wallet uses your private key to produce a signature that proves you authorised the spend — without ever exposing the key itself. Every node checks that signature before it accepts the transaction.
Seed phrase
A seed phrase is a human-readable backup of your private key — 12 or 24 words, usually. Write it down offline and keep it safe. Lose the seed and lose the device, and your coins are gone for good.
Nodes & consensus
MoonBite's rules are enforced by every node running the software — not by one company, not by one server.
What a node does
A full node pulls every block since genesis, checks each one against the protocol rules, and passes valid blocks and transactions to its peers. It's the software that actually decides what MoonBite is.
Consensus without a leader
Nodes agree on the chain by each following the same rules on their own. No vote, no administrator, no head office. Break a rule and every node that sees your block rejects it — doesn't matter who produced it.
Why run your own?
Lean on someone else's node and you're trusting them to run the rules right. Run your own and you get a direct, unmediated view of the real chain. No block gets accepted on faith — you check it.
The fixed supply schedule
Every MBITE that will ever exist is minted by miners, on a schedule written into the protocol at launch. No knob to turn later.
Hard cap: ~33,000,000 MBITE
The protocol will never mint more than this. The cap falls out of the halvings: rewards cut in half every 1,650,000 blocks, creeping toward zero without ever quite touching it.
Block subsidy starts at 10 MBITE
The genesis block carries a 10 MBITE reward, paid in full to the miner who found it. No premine: not one coin existed before public mining began.
Halving every 1,650,000 blocks
At the 2-minute block target, 1,650,000 blocks takes roughly 6.27 years. Each halving cuts the reward in half and permanently slows the rate of new issuance. It only goes one direction.