// Mangonote Docs
Everything you need to run, mine, and stay untraceable.
Mangonote (MNN) is a pure proof-of-work currency: fairly launched on February 11, 2024, CPU-mineable via RandomX, private by default, with 60-second blocks and a hard cap of 100,000,000 MNN.
Introduction#
Mangonote is designed around four commitments: fairness (no premine — every coin was mined in the open from block zero), accessibility (RandomX makes CPUs the best mining hardware, so no ASIC arms race), privacy (sender, receiver and amount are obscured on every transaction), and speed (a 60-second block time — on average ~204× faster confirmations than Bitcoin).
Block size is dynamic and fees are computed automatically, so you never configure either. There is no foundation allocation and no instamine — just hashes.
At a glance#
| Property | Value |
|---|---|
| Ticker | MNN · 11 decimals |
| Consensus | Proof of Work · RandomX |
| Block time | 60 seconds |
| Max supply | 100,000,000 MNN |
| Premine | None |
| Fees | Automatic |
New here
Short on time? Follow the Quickstart — five commands from zero to a synced node and a fresh wallet.
Quickstart#
Watch the whole first-run flow — download, sync, wallet creation — then reproduce it on your own machine.
Requirements#
- OS: Linux (x86-64/ARM64), macOS 12+, or Windows 10+ (use WSL2 for the CLI tools).
- RAM: 2 GB minimum for RandomX — the algorithm is memory-hard by design.
- Disk: ≈48 GB for a full node, ≈18 GB with
--prune-blockchain. - CPU: anything from the last decade. A Raspberry Pi 5 can run a node.
Verify your download
Always check the SHA-256 checksum before running a binary: sha256sum mangonote-linux-x64.tar.bz2 — compare against the value published on mangonote.org.
Running a node#
Why run your own node#
Your node validates every block and every signature locally. Wallets that rely on third-party servers leak which addresses you own; a local node leaks nothing. For the strongest privacy, run a node — a pruned one fits on a laptop.
# start the daemon (mainnet) — first run syncs the chain
./mangonoted
# save ~60% disk with a pruned node
./mangonoted --prune-blockchain
# or run detached and check on it later
./mangonoted --detach
./mangonoted status
Config file & common flags#
Everything the daemon accepts as a flag can live in ~/.mangonote/mangonote.conf:
# data directory for the blockchain
data-dir=/mnt/chain/mangonote
p2p-bind-port=18180
rpc-bind-port=18181
# protect the RPC if you bind it externally
rpc-login=user:change-me-long-password
prune-blockchain=1
max-concurrency=4
| Flag | Effect |
|---|---|
| --prune-blockchain | Drop old transaction data; keeps full validation history. |
| --data-dir | Where the chain and wallet caches are stored. |
| --rpc-login | user:password for the RPC interface (recommended if exposed). |
| --add-peer | Seed a specific peer, e.g. 203.0.113.7:18180. |
| --max-concurrency | Cap CPU threads used by the daemon. |
| --detach | Fork to background; check with status. |
What healthy logs look like#
2025-06-14 21:07:33.552 [node0] INFO cn Height 898,415 · difficulty 214,551 · 8 peers
2025-06-14 21:07:52.013 [node0] INFO cn Block #898,416 accepted · reward 12.45 MNN
2025-06-14 21:08:04.381 [P2P6] INFO net Peer handshake ok · 9 outgoing · 7 incoming
Tip
Type status inside the daemon console any time — it prints height, difficulty, peer count and current hashing status without leaving the process.
CPU mining#
Mangonote uses RandomX, a proof-of-work algorithm optimized for general-purpose CPUs. It runs your processor through thousands of randomly generated programs against a 2 GB memory dataset — which is exactly why GPUs and ASICs gain so little here. GPU mining is possible, but not efficient; the CPU you already own is the right tool.
Get XMRig#
The reference RandomX miner works out of the box. Grab a release build, or compile it for maximum performance:
# build from source (recommended)
git clone https://github.com/xmrig/xmrig && cd xmrig && mkdir build && cd build
cmake .. && make -j$()nproc
# linux: enable huge pages for the fast mode
sudo sysctl vm.nr_hugepages=1168
Configure & run#
Point XMRig at your local daemon for solo mining, or at a pool (next sections). Set your payout address as the user:
{
"autosave": true,
"cpu": { "enabled": true, "huge-pages": true },
"randomx": { "mode": "fast" },
"http": { "enabled": true, "host": "127.0.0.1", "port": 8080 },
"pools": [
{
"coin": "mnn",
"url": "localhost:18181",
"user": "YOUR_MANGONOTE_ADDRESS",
"pass": "rig-01"
}
]
}
$ ./xmrig -c config.json
What to expect#
Indicative RandomX hashrates at default tuning — your numbers will vary with memory speed and BIOS settings:
| CPU | Threads | Hashrate | RAM |
|---|---|---|---|
| Ryzen 9 7950X | 16 | ~19.5 kH/s | 32 GB |
| Ryzen 7 5700X | 8 | ~9.1 kH/s | 16 GB |
| Core i5-12400 | 6 | ~5.4 kH/s | 16 GB |
| Apple M2 | 4 | ~3.8 kH/s | unified |
| Raspberry Pi 5 | 4 | ~0.4 kH/s | 8 GB |
Before you start
Mine to a wallet you control, keep an eye on thermals, and note that sustained fast-mode mining will make a laptop's fans very vocal. One mining thread wants its own L3 cache slice and a share of the 2 GB dataset.
Solo mining#
Solo mining means your own daemon assembles block candidates and you search for a valid hash alone. Every block you win pays the full reward plus fees — currently 12.45 MNN + fees — straight to your address. Payouts are instant because there is no intermediary, but income is lumpy: with a modest hashrate you may wait days between blocks.
mangonoted> start_mining 8
Mining started: 8 threads → mNNq…8fKz
mangonoted> stop_mining
Mining stopped.
- Good for: supporting the network's decentralization, lottery-style rewards, no pool fees.
- Not good for: predictable income — variance is the price of the full block reward.
Pool mining#
Pools aggregate hashrate from many miners and split rewards proportionally, smoothing income into small, steady payouts. Community pools use PPLNS with a typical minimum payout of 0.1 MNN.
"pools": [
{ "coin": "mnn",
"url": "pool.mangonote.org:3333",
"user": "YOUR_MANGONOTE_ADDRESS",
"pass": "x",
"rig-id": "living-room" }
]
Monitor your rig
With the built-in HTTP API enabled, open http://127.0.0.1:8080 for live hashrate, accepted shares, and temperature per core.
CLI wallet#
Create a wallet#
The CLI wallet generates a key pair and writes a 25-word seed — the master key to your funds. It is shown once at creation.
$ ./mangonote-wallet-cli
Wallet file name: juice
Password for new wallet:
Generated new wallet: mNNqYs9dK7…8fKz
View key: c1e4…9ab0
NOTE: the following 25 words can be used to recover access to your wallet.
Write them down and store them somewhere safe and secret.
Everyday commands#
| Command | What it does |
|---|---|
| balance | Unlocked vs. total balance (new funds unlock after ~10 confirmations). |
| address | Show your receive address(es). |
| transfer <addr> <amt> | Send MNN — fee and privacy handling are automatic. |
| sweep_all <addr> | Empty the wallet into a single destination. |
| show_transfers | In/out history with tx hashes. |
| seed | Re-display the 25-word seed. Keep it secret. |
| refresh | Rescan the chain for incoming transactions. |
The seed is the wallet
Anyone holding the 25 words holds the funds — no password resets, no support desk. Write them on paper, store them offline, and never type them into a website.
Restore & backup#
Twenty-five words are all you need to rebuild a wallet on any machine. Supplying a restore height makes the scan fast — the wallet starts looking for your transactions from that block instead of from genesis:
$ ./mangonote-wallet-cli --restore-deterministic-wallet \
--electrum-seed "lizard oxygen mango … (25 words)" \
--restore-height 898000
- File backup: copy
<wallet>.keysplus the wallet file and password — that restores everything without the seed. - Don't know your first tx? Use the height from around your first deposit; a slightly early guess just costs a longer scan.
- Test it: restore into a fresh directory once, now, while nothing is on fire.
Addresses#
A Mangonote address is a 106-character string beginning with m (e.g. mNNq…8fKz). It is safe to share — receiving funds reveals nothing about you on-chain. Three flavors exist:
- Standard address — your default receive address.
- Subaddress — derived indexes for per-contact or per-service receiving, all spending to the same wallet.
- Integrated address — a standard address with an embedded payment ID, useful for exchanges.
Privacy habit
Give every service its own subaddress. Linkability between your payments then ends at your wallet — which observers cannot open.
Privacy#
Mangonote is private by default, for everyone, on every transaction. There is no opt-in mode and no "transparent" fallback to misconfigure. Three independent techniques stack to break every link an observer would normally draw:
Stealth addresses — hides the receiver
Every payment is sent to a one-time address derived from the recipient's key. The chain never records your actual address, so incoming payments can't be clustered or looked up.
Ring signatures — hides the sender
Each input is signed against a ring of decoy outputs plucked from the chain. Verification proves you own one of them — not which — so transaction graphs dissolve into plausible anonymity sets.
Range proofs — hides the amount
Cryptographic range proofs (bulletproof-style) show that amounts are non-negative without revealing them. Balances reconcile; values stay confidential.
Privacy in practice#
Protocol privacy is necessary but not sufficient. Two habits close the remaining gaps: use your own node (so you don't ask someone else's server about your transactions) and avoid address reuse (subaddresses make that painless). With both, the only party who knows what you sent, received, or hold is you.
Fees & scaling#
You never pick a fee by hand. The wallet computes it from current network conditions — median recent block size and mempool pressure — and attaches the smallest fee that reliably lands in the next block or two. Typical transactions cost a fraction of a cent in MNN terms.
Fee priority#
Impatient? A priority multiplier multiplies the computed fee to outbid congestion:
| Priority | Multiplier | Typical fee* | Expect confirmation |
|---|---|---|---|
| Auto (default) | computed | ~0.001 MNN | next 1–2 blocks |
| Normal | ×1 | ~0.0009 MNN | 1–3 blocks |
| Elevated | ×4 | ~0.0036 MNN | next block |
| Priority | ×20 | ~0.018 MNN | next block, first cut |
* indicative, 1-in/2-out transaction. Network conditions vary.
Dynamic block size#
Blocks are not capped at a fixed byte count. Each new block may exceed the median of recent blocks by a bounded factor, letting capacity grow under sustained demand — and shrink back when quiet — while full nodes retain validation headroom. Combined with automatic fees, scaling stays an emergent property rather than a governance debate.
Consensus#
A transaction's journey: broadcast → mempool → a miner's block template → RandomX hashing until a candidate meets the network difficulty → propagation and validation by every node. Once included, 10 confirmations (~10 minutes) is the community-recommended threshold for treating a payment as settled — roughly a coffee's length, not an hour.
Difficulty retargets every block using a linearly-weighted moving average, so hashrate swings smooth out within minutes rather than requiring 2016-block epochs.
Security after full emission: when the 100,000,000th MNN is mined, the block subsidy ends — miner revenue transitions to the fee market that has been accruing since launch (over 26,600 MNN in fees paid to miners so far).
Specifications#
| Parameter | Value |
|---|---|
| Launch date | February 11, 2024 |
| Premine | None |
| Consensus | Proof of Work · RandomX |
| Block time | 60 seconds |
| Block reward | 12.45 MNN (at current height) |
| Max. supply | 100,000,000 MNN |
| Decimals | 11 — smallest unit 10⁻¹¹ MNN |
| Block size | Dynamic (median-based) |
| Difficulty | LWMA, retarget every block |
| Recommended confirms | 10 (~10 min) |
| P2P port | 18180 |
| RPC port | 18181 |
| Ticker | MNN |
Live network figures — height, total mined, total fees — are on the main site and the block explorer.
FAQ#
Can I mine on a GPU?+
Technically yes, practically no. RandomX is memory-hard and tuned for CPU microarchitecture; a modern GPU mines worse per watt than a mid-range CPU. Save the GPU for rendering — mine on the CPU you already own.
What happens after all 100M MNN are mined?+
The block subsidy ends and miner revenue shifts to transaction fees, which have accrued since launch. Fees are paid to whichever miner wins each block, so the security budget continues without inflation.
Why does my balance say "locked"?+
Newly received funds need ~10 confirmations (about 10 minutes at 60-second blocks) before the wallet lets you spend them again. This prevents chain-reorganization double-spends. They unlock automatically.
Do I have to run a full node?+
No — but you should. Remote nodes can correlate your wallet's view requests with your IP. A pruned node fits on a laptop, and the daemon does the rest. Your privacy floor is your own hardware.
How do I check a transaction?+
Search the tx hash on the block explorer at explorer.mangonote.org. You'll see it exists, its height and its fee — amounts and counterparties stay hidden by design, even in the explorer.
Is mining profitable on my laptop?+
It's profitable in understanding. Enable huge pages, run fast mode, and watch your kH/s. Just monitor temperatures, and don't expect to retire on a 4-core — solo mine for the lottery thrill, or join a pool for steady dust.
Where do I get help or report a bug?+
The #support channel on Discord is the fastest route for questions; protocol bugs are best reported with a reproducible case and your daemon version (mangonoted --version).
Community#
Miners, makers, and the mildly obsessed — the grove is open 24/7.
Was this page helpful?