# MoonBite Core — Release Binaries

MoonBite (**MBITE**) is a proof-of-work Layer-1 coin, forked from Litecoin Core v0.21.5.5.
These are Linux x86-64 binaries built on Ubuntu 22.04 (glibc 2.35).

## Chain parameters

| Parameter        | Value                        |
|------------------|------------------------------|
| Ticker           | MBITE                          |
| PoW algorithm    | RandomX (CPU-friendly, ASIC-resistant) |
| Max supply       | just under 33,000,000 MBITE  |
| Block time       | 2 minutes (120 s)            |
| Difficulty retarget | every 60 blocks (~2 h), 4x clamp |
| Initial reward   | 10 MBITE                     |
| Halving interval | 1,650,000 blocks (~6.27 years) |
| Address prefix   | bech32 `moon1…` (testnet `tmoon1…`, regtest `rmoon1…`); legacy P2PKH `M`, P2SH `3` |
| P2P port         | 9444 (mainnet) / 19555 (testnet) / 19444 (regtest) |
| RPC port         | 9445 (mainnet) / 19445 (testnet) / 19443 (regtest) |

### Genesis blocks (baked in)
- **mainnet** `ffe25d9248b7f56d8934719ed5c7357f7595451c4b9d391d9b8377e62a83e39c` (public-launch genesis, stamped 2026-10-17 09:00 CEST so no block can exist before the 07:00 CEST launch; network magic `e2 9b 4d 4d`; all prior chains — the beta, `18a76cd4…`, `7b93fff9…` and the unmined `082d5e52…` — are NOT valid on this network)
- **testnet** `5c2a77cdb0cab1697ca99b770dd0c6acc28baa241b98403587a0355ed58356bc` (nonce 4200)
- **regtest** `61dc2ef13c0f0f26a9a90c7f34d09578f10e8490687d1314f97233e525f2fe99` (nonce 0)

## Contents (`bin/`)
- `moonbited` — full node daemon
- `moonbite-cli` — RPC command-line client
- `moonbite-qt` — **desktop GUI wallet** (Qt5)
- `moonbite-tx` — raw transaction utility
- `moonbite-wallet` — offline wallet tool

### Windows x86-64 (`bin/*.exe`)
- `moonbited.exe`, `moonbite-cli.exe`, `moonbite-tx.exe`, `moonbite-wallet.exe`
- Cross-built with mingw-w64 (POSIX threads, static libstdc++/winpthread). Depend only on
  system DLLs (kernel32, ws2_32, advapi32, shell32, iphlpapi, msvcrt) — no runtime installer needed.
- Headless build: no `moonbite-qt.exe` yet.
- Verified on Windows 11: daemon starts, mines RandomX regtest blocks, shuts down cleanly.
- `miner/mine.ps1` expects `moonbited.exe` and `moonbite-cli.exe` next to it; copy them in or
  point the script at `bin/`.

Verify downloads against `SHA256SUMS.txt`.

## User downloads: two archives, always separate

Per `docs/ADR-013-miner-distribution-policy.md` the miner and the wallet are
never shipped in the same archive, and nothing MoonBite publishes mines in a
browser or installs itself to run at startup.

| Archive | Built from | Contains |
|---|---|---|
| `moonbite-miner-<os>-<arch>.zip` / `.tar.gz` | `release/miner/` | `moonbited`, `moonbite-cli`, `mine.ps1` + `Mine-MoonBite.bat` (Windows) or `mine.sh`, `README.md`, `ANTIVIRUS.md`. No wallet. |
| `moonbite-wallet-<os>-<arch>.zip` / `.tar.gz` | `release/wallet/` | the desktop wallet app and its `README.md`. No node, no miner, no scripts. |

Build both (Windows) with:

```bash
python deploy/miner/build-windows-bundle.py            # miner + wallet, if inputs present
python deploy/miner/build-windows-bundle.py --artifact miner
python deploy/miner/build-windows-bundle.py --artifact wallet
```

Output goes to `release/dist/` with one `SHA256SUMS.txt` covering every archive
and every `.exe` inside them. Linux: `deploy/publish-node-binaries.sh` emits
`moonbite-miner-linux-x86_64.tar.gz` next to the bare node binaries. Sign the
manifest with minisign and submit new executables to the AV vendors
(`release/miner/ANTIVIRUS.md`) before publishing.

Build rules for anything PyInstaller-based (`moonbite.spec`,
`wallet-desktop/README.md`): no UPX, one-directory not `--onefile`, Windows
version resource from `windows-version-info.txt`.

## Desktop wallet
Launch the GUI wallet with `./bin/moonbite-qt` (mainnet) or `./bin/moonbite-qt -testnet`.
It runs an integrated node and reports client name `MoonBiteCore` on the network.

## Quick start (regtest — instant local mining)
```bash
./bin/moonbited -regtest -rpcuser=<user> -rpcpassword=<strong-password> -daemon
CLI="./bin/moonbite-cli -regtest -rpcuser=<user> -rpcpassword=<strong-password>"
$CLI createwallet "wallet"
ADDR=$($CLI getnewaddress)
$CLI generatetoaddress 101 "$ADDR"   # mine 101 blocks (coinbase matures at 100 blocks, ~200 min on mainnet)
$CLI getbalance                      # -> 10.00000000
$CLI sendtoaddress <dest_addr> 2.5  # send MBITE
$CLI stop
```

## Mainnet / testnet
1. Copy `moonbite.conf.example` → data dir as `moonbite.conf`, set a strong `rpcpassword`.
2. `./bin/moonbited` (mainnet) or `./bin/moonbited -testnet`.
3. See the repo `docs/` for mining, wallet, node-setup, and exchange-listing guides.

## Verified working
- **Mining:** RandomX PoW, regtest mined 101 blocks → 10 MBITE coinbase matured.
- **Transactions:** send/receive confirmed (2.5 MBITE between two wallets, mempool → block).
- **P2P networking:** two nodes connect and sync a 10-block chain (identical tips).
- **Wallet security:** AES-256 encryption, passphrase-locked spending, HD seed, backup — all verified.
- **Block explorer:** wired to a live node, serves real block/tx data (no demo mode).
- **Branding:** `--version` reports **MoonBite Core**; window title / About dialog say
  "MoonBite Core"; network client name `MoonBiteCore` (`/MoonBiteCore:0.21.5.5/`);
  default data directory is `.moonbite` (Linux) / `MoonBite` (Windows/macOS).

## Status / known remaining polish
- Mainnet has no DNS seeds yet (removed Litecoin's); use `deploy/` to stand up seed
  nodes on VPS hosts, then bake their IPs into chainparams before public launch.
- A few deep-menu Qt labels may still read "Litecoin" (cosmetic); core identity,
  version banner, About dialog, and data dir are all MoonBite.
- macOS/Windows native builds require cross-compiling (these are Linux x86-64).

Forked chain — **not** affiliated with or compatible with the Litecoin network
(distinct magic bytes, ports, genesis, and address prefixes).