[ANN] Orange (OAG) | RandomX CPU-only | No premine | Solo mining | Rust

[oag-manh]

Orange (OAG)

A small CPU-mined UTXO coin. RandomX proof of work, written in Rust.
No premine, no ICO, no price — just a coin you can mine on your own PC.

Website | Explorer | Web wallet | Download | Source | Discord

Latest version: v0.1.4 — questions and chat on Discord

What this is
Orange is a plain UTXO blockchain: no smart contracts, no script language, no privacy features. It is a hobby project by one university student in Japan. Mainnet has been running since September 2026 with a handful of miners, and I am looking for people who will mine it, run nodes, or just try it out.

Live numbers (hashrate, holders, how the coins are spread) are on the explorer: explorer.oagcoin.org/stats

What this is not

• There is no exchange listing and no price. You mine it and hold it.
• There is no ICO, no premine and no developer reward. I mine under the same rules as everyone else.
• I am not selling anything and I will never ask you for money.

About AI
Much of the code was written with an AI assistant (Claude). The commit history shows this openly. I made the design decisions and reviewed the changes, and the specification explains the reasoning behind each rule.

Specifications

Proof of work	RandomX (CPU)
Accounting	UTXO
Signatures	Schnorr / BIP340 (secp256k1)
Block time	60 seconds
Difficulty	LWMA, every block
Block reward	10 OAG, flat, no halving
Coinbase maturity	120 blocks (about 2 hours)
Max supply	1,000,000,000 OAG (emission ends after about 190 years)
Premine	0 (the 10 OAG in the genesis block is unspendable)
Genesis timestamp	2026-09-01 00:00 UTC (block 1 was mined on 2026-09-17)
P2P port	9444

Try it in 1 minute: the web wallet
Open wallet.oagcoin.org, create a wallet, and you have an OAG address. Nothing to install.
Your recovery phrase and keys are created and kept in your browser; the server only sees signed transactions. Still, a web page can be tampered with, and the server can see which addresses you look up, so use it for small amounts. For anything larger, run your own node (it has the same wallet built in: add --wallet).

Mining (Windows)
There is no pool and no XMRig support. The miner is built into the node, so everyone who mines is also running a full node. That is on purpose: with so few participants, every miner also keeps the network alive.

1. Download orange-windows-x86_64.zip from the latest release and unpack it.
2. Check the file against the .sha256 next to it:

Code:

Get-FileHash orange-windows-x86_64.zip -Algorithm SHA256

3. Create a wallet. It asks for a passphrase (at least 8 characters), then prints your receiving address and a 12-word recovery phrase. Write the phrase down on paper. It may be shown only once. No running node is needed for this step.

Code:

.\oag-wallet.exe new --network mainnet

4. Start mining to that address. --mining-threads 0 uses every core. --fast uses 2 GB of memory shared by all threads and hashes much faster; without it, each thread uses 256 MB.

Code:

.\oag-node.exe run --network mainnet --mine --fast --payout <your address> --mining-threads 0

5. Check your balance. A mined reward becomes spendable after 120 blocks. Each block you find adds one coin to the wallet, so fold them together about once a week:

Code:

.\oag-wallet.exe balance --network mainnet
.\oag-wallet.exe consolidate --network mainnet

Linux (x86_64) and Raspberry Pi / ARM builds are in the same release; the Linux steps are on the website. There is no macOS build; build from source (see the README).

Low on disk? Add --prune. The node still checks everything but keeps only the last few days of blocks. Mining and --wallet both work on a pruned node (the wallet just shows no history).

Not mining? Running oag-node run --network mainnet without --mine validates and relays blocks, and that already helps. Since v0.1.4 the node asks your home router (UPnP / NAT-PMP) to open port 9444 by itself, so other nodes can connect to you without manual port forwarding. Turn it off with --no-portmap.

Explorer
Public explorer: https://explorer.oagcoin.org — search for your payout address; each row marked "mined" is a block you found. /stats shows the network, /richlist the largest addresses.

You can also run your own: add --explorer to the command you already run (do not start a second node). The first time it builds an index; then open http://127.0.0.1:8080/ on the same computer.


Latest release: v0.1.6 (release notes)
Optional update, no consensus changes. 0.1.2 and later keep working on the same chain.

• Public web wallet at wallet.oagcoin.org (small amounts).
• Browser wallet: address list, choose the sending address, live updates, phone fixes.
• Since v0.1.4: the node opens its port on your home router by itself (UPnP / NAT-PMP); explorer /stats and /richlist.

To upgrade: stop the node, replace oag-node and oag-wallet, start it again. Your data is kept; no resync.

Behind a home router? After starting v0.1.4, look for the router (UPnP) forwards … (or (NAT-PMP)) in the log. If it isn't there, please post what the log says about port mapping — reports from different routers help.

Looking for seed node operators
New nodes find their first peers through the DNS seed seed.oagcoin.org. Right now every seed sits behind my own domain, so new nodes depend on me. I would like to fix that.

• Easy way: if you run a node 24/7 with a static public IPv4 address and port 9444 open, post your IP here, on Discord, or in a GitHub issue. After checking it is reachable, I will add it to seed.oagcoin.org. Start your node with --external-addr <your IP>:9444.
• Better way: if you also have a domain, point it at your node and open a pull request adding it to MAINNET_SEEDS in crates/oag-node/src/seeds.rs. Seeds run by different people mean the network does not depend on me or my domain.

A seed's IP address is public by nature. There is no reward; it is purely volunteering.

Official places
The GitHub repository, this thread, and the Discord server. Any other Discord server or Telegram group is not official.

• Nobody from the project will message you first, and nobody will ever ask for your recovery phrase.
• Download binaries only from GitHub releases. The only official web wallet is wallet.oagcoin.org.
• Anything I post as the developer can be checked against a signature from the address block 1 paid (oag-wallet verify).

Honest notes

• The network is tiny. Right now it depends heavily on my own nodes, which is exactly what I want to change.
• The code has not been audited by anyone else.
• The specification is written in Japanese first; the English version is a translation. Comments in the source code are in Japanese.
• Orange started from chroma.

Links

• Website: https://oagcoin.org
• Explorer: https://explorer.oagcoin.org
• Web wallet: https://wallet.oagcoin.org
• Source: https://github.com/manh923/Orange
• Releases: https://github.com/manh923/Orange/releases/latest
• Specification (English): https://github.com/manh923/Orange/blob/main/docs/SPEC.en.md
• Discord: https://discord.gg/72KWbXkn86
• Contact: contact@oagcoin.org
• Over Tor: website vwywoti2deynriolwomkz23djczsxqag342fkckum5riugwtt3xwz5ad.onion, explorer tsdg74bfpuvw62vhdn5cw75smdhqtd2q5ex4onxaelpguvzqme6dqzid.onion

English is not my first language. I use translation tools, so please be patient with my replies. Questions, bug reports and criticism are all welcome — the fastest place is Discord.
I am in Japan (UTC+9), so replies may take up to a day.

[oag-manh]

There is no Discord yet. For now, please ask here in this thread, or open an issue on GitHub. While the project is this small, I would like to keep everything in one public place. If more people join, I will set one up.

[drywall777]

Hello.

Please forgive me if I ask a simple question.  I can't get the command for the explorer to work.  I either get the node is already running error or page not found in my browser.  Please help me so I can see what my miners are accomplishing.  Thanks.

[oag-manh]

Thanks for mining, and it is not a simple question at all. My instructions were misleading, sorry.

The explorer is not a separate program. It is a flag on the node you are already running. Two nodes cannot share the same data folder, which is why you got the "already running" error.

1. Stop your mining node (Ctrl+C).
2. Start it again with --explorer added to the same command:

Code:

.\oag-node.exe run --network mainnet --mine --payout <your address> --mining-threads 0 --explorer

3. The first time, it scans the whole chain to build an index. Wait until it prints:

Code:

explorer open at http://127.0.0.1:8080/

4. Open http://127.0.0.1:8080/ in a browser on the same computer, and paste your payout address into the search box. That page shows what your miners have earned.

The explorer only listens on that computer, so you cannot open it from another machine. If you mine on several computers with the same payout address, one explorer is enough: every block they find will show up under that address.One more thing I forgot to mention: on the address page, look at the "unspent outputs" table at the bottom. Every row marked "mined" is one block that address found, and the "height" column shows which block it was. Each block pays 10 OAG (plus any fees). My English comes from Google Translate, so it may sound a little unnatural, but thank you for running the node.

[csriche10]

My name is Riche
I'm The Co-founder  of CryptoSky Platform. CryptoSky is a advertising/partnership platform since 2018. We are marketing in discord, Twitter, telegram. We have 140+ clients & partners with 130+ marketing projects & 65+ partners projects.



Discord :  https://discord.gg/wmE5ANXD4Y
For partnership/marketing info
Contact : CS Riche (CO-FOUNDER)

[oag-manh]

Interested in some Apple Silicon mining software.

There is no prebuilt macOS binary, but it builds from source on Apple Silicon. The release workflow compiled it on GitHub's Apple Silicon runner before I dropped macOS from the release list. I have not mined on a Mac myself, so please tell me how it goes.

Code:

brew install cmake
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
git clone https://github.com/manh923/Orange
cd Orange
cargo build --release -p oag-node -p oag-wallet

The binaries end up in target/release/. After that the steps are the same as on Windows, without ".exe":

Code:

./target/release/oag-wallet new --network mainnet
./target/release/oag-node run --network mainnet --mine --payout <your address> --mining-threads 0

[drywall777]

Hello.

my command ---   .\oag-node.exe run --network mainnet --mine --payout oag1..........8hlw4pln8syjaawd82swpd5jsmv0m..........xxxxxxxxxx --fast --mining-threads 6 --explorer

result ---   error: cannot listen for the explorer on 127.0.0.1:8080: Only one usage of each socket address (protocol/network address/port) is normally permitted. (os error 10048)

After adding --explorer to the end of my mining command line, I still get the can't run more than one instance error.  Windows 11.  Powershell command window. I have a node running on both of my mining computers.  I wonder if that is the issue.

Other than me not being able to figure out the explorer issue, the miner is running smoothly. Thanks.

[oag-manh]

error: cannot listen for the explorer on 127.0.0.1:8080: Only one usage of each socket address ... (os error 10048)

Thanks for testing it! Error 10048 means something on that PC already holds port 8080. I think it is your other node: you don't need a separate node for mining. One oag-node process does everything — it is the node, the miner and the explorer at the same time. Two of them on one PC also fight over the P2P port 9444 and the chain database, which is why you see the "one instance" error.

So on each computer, stop the other node (close its window or Ctrl+C), then run just this one:

Code:

.\oag-node.exe run --network mainnet --mine --payout oag1... --fast --mining-threads 6 --explorer

and open http://127.0.0.1:8080/ in a browser.

If some other program is using 8080, give the explorer a different port:

Code:

--explorer 127.0.0.1:8081

Also, if both computers mine to the same payout address, that is fine. Each one is a full node on its own.

[BoozyTalking]

PoW is not a RandomX, you lie, hashrate is to low for RandomX.

[oag-manh]

PoW is not a RandomX, you lie, hashrate is to low for RandomX.

It is RandomX — the same tevador/RandomX C++ library Monero uses, called through randomx-rs. See crates/oag-pow/src/randomx.rs.

It is slower than XMRig because the built-in miner does not use huge pages, and without --fast it mines in light mode. The network hashrate is low because very few people mine it yet.

[oag-manh]

v0.1.1 released — https://github.com/manh923/Orange/releases/tag/v0.1.1

What changed

1. Fast mode now shares one dataset across all threads.
Until 0.1.0, every mining thread built its own 2 GB RandomX dataset, so 6 threads took about 12 GB and built the dataset 6 times. Now there is one 2 GB dataset shared by all threads, the same way Monero and XMRig do it. Each extra thread only adds 2 MB.

Mode	1 thread	6 threads (0.1.0)	6 threads (0.1.1)
light	256 MB	1.5 GB	1.5 GB
fast	2 GB	12 GB	2 GB

So with --fast you can just pass --mining-threads 0 to use every core.

Thanks to drywall777 for mining with 6 threads — that is what made this obvious.

2. Large pages.
The dataset is put in large pages when the OS allows it. If it cannot get them, it quietly falls back to normal pages and keeps mining. The log tells you which:

Code:

mining with 6 threads (fast mode, large pages)

To enable them (one-time setup):

Linux:

Code:

sudo sysctl -w vm.nr_hugepages=1168
echo 'vm.nr_hugepages=1168' | sudo tee /etc/sysctl.d/90-orange.conf

Windows (Pro and above): run secpol.msc → Local Policies → User Rights Assignment → Lock pages in memory → add your account, then sign out and back in. Windows Home does not have secpol.msc; it simply mines on normal pages.

Upgrading

No consensus change. 0.1.0 and 0.1.1 nodes talk to each other and agree on every block. Stop the node, replace the binaries, start it again with the same command. Your data directory and wallet are kept as they are.

Downloads

• Windows: orange-windows-x86_64.zip
• Linux: orange-linux-x86_64.tar.gz
• Raspberry Pi / ARM: orange-linux-aarch64.tar.gz

Each has a .sha256 next to it. macOS: build from source (steps in the README).

I have not published hashrate numbers because they depend on the machine. If you try it, I would be glad to hear what you get.

[BoozyTalking]

Now is much better.

[oag-manh]

thank you!

[AliErkic]

Nice project, Sir!

[oag-manh]

One request: if you have port 9444 open and a static IP, could you restart your node with this option added?

--external-addr <your global IP>:9444

This lets other nodes learn your address so they can connect to you, and it makes the network less dependent on me. Thanks!Thank you! You're right — right now it's not easy for normal users. You need the command line, open ports, and so on.

The code is open source (MIT), so anyone who wants to help is welcome: a GUI wallet, better docs, installers, anything. You don't need my permission. Fork it, build it, or send a pull request on GitHub.

I don't plan to form an official team or collect funds. I'd like Orange to grow the way Bitcoin did: people build what they need, and the good things spread on their own.

[Sergick2023]

How start mine?.\oag-node.exe run --network mainnet --mine --payout <address> --mining-threads 0 --explorer --fast
Right?

This right way?

[oag-manh]

Yes, that's right! Just replace <address> with your own OAG address. If you don't have one yet, add --wallet and open http://127.0.0.1:25565/ to create one.

--fast needs about 2 GB of free RAM. If your PC has less, remove --fast and it will mine in light mode instead.

This is normal process?
http://

Yes, that's normal. 127.0.0.1 means your own PC. The page never leaves your computer, so nothing travels over the internet and there is nothing to intercept. Bitcoin Core and other wallets use local http pages the same way. Your browser may show "Not secure"; that's expected for any http page.

Just don't make port 25565 reachable from outside. The node itself refuses to open the wallet on a non-local address without a TLS certificate.Looking for volunteers to run public nodes.

If you have a static IP, can keep a node running most of the time, and can open port 9444/tcp, please start your node with:

--external-addr <your global IP>:9444

Your address will then spread to other nodes, and new users can sync from you instead of only from the seed.

If you're willing to go one step further, reply here (or PM me) with your IP and I'll add it to seed.oagcoin.org. Only do this if you're fine with your IP being public — every node's IP is visible to its peers anyway.

[drywall777]

Hello.

Just an update about the explorer issue.  I just had to find a port that wasn't being used by something else.  Also was able to configure the browser wallet with the instructions on your releases pages.  Thank you for your time.  I'm mining with no issues now.  The 2GB per entire session has enabled me to mine with more threads because of the lower amount of system RAM needed. Thanks.

[andremangra]

Hello!

Congrats, it's a good project!

I am doing a read-only, independent check of Orange mainnet history. Could two node operators who are independent of the project publish comparable chain data? No mining or wallet information is needed.

Please include your UTC collection time, software version/commit, whether your node is full or pruned, and whether it is synced. From your own local RPC, please share `getinfo`; for heights 0–100, `getblockhash [height]` and `getblockheader [hash]`; and, if you retain those bodies, `getblock [hash,false]` for heights 0–100 (or a downloadable text file with those results). The raw blocks let others inspect coinbase outputs and reproduce hashes. Please also include the latest tip's `getblockheader` at the same collection time. If posting all 101 blocks is inconvenient, a public file with a SHA-256 digest and a link is fine.

Please identify whether the node is yours or operated by the project, so the sources can be counted correctly. There is no need to publish your IP address, RPC cookie, data directory, wallet files, private keys, recovery phrase, or logs. Please do not expose RPC to the Internet for this request. I will compare genesis, parent links, timestamps, difficulty, cumulative work, tip agreement, and early coinbase payouts without assuming wrongdoing.

[oag-manh]

Hello!

Congrats, it's a good project!

I am doing a read-only, independent check of Orange mainnet history. Could two node operators who are independent of the project publish comparable chain data? No mining or wallet information is needed.

Please include your UTC collection time, software version/commit, whether your node is full or pruned, and whether it is synced. From your own local RPC, please share `getinfo`; for heights 0–100, `getblockhash [height]` and `getblockheader [hash]`; and, if you retain those bodies, `getblock [hash,false]` for heights 0–100 (or a downloadable text file with those results). The raw blocks let others inspect coinbase outputs and reproduce hashes. Please also include the latest tip's `getblockheader` at the same collection time. If posting all 101 blocks is inconvenient, a public file with a SHA-256 digest and a link is fine.

Please identify whether the node is yours or operated by the project, so the sources can be counted correctly. There is no need to publish your IP address, RPC cookie, data directory, wallet files, private keys, recovery phrase, or logs. Please do not expose RPC to the Internet for this request. I will compare genesis, parent links, timestamps, difficulty, cumulative work, tip agreement, and early coinbase payouts without assuming wrongdoing.

Thanks for doing this. Independent checks are exactly what a new chain needs.

I'm the developer, so my node doesn't count as independent. I'll leave the data to other operators. The strongest check doesn't need anyone's data, though: build from source (or use the release binaries and compare their SHA-256), sync from scratch, and query your own RPC. Every node re-verifies all PoW and rules from genesis, so the chain you end up with is checked by your own machine.

To save you time on the early coinbase payouts: I mined alone from block 1 (Sept 17) until I posted this thread (Sept 24). Almost all blocks before the announcement went to my address oag1qnke7nepxawzz8zepfl2eq8qfe4tzjkvcr8tsyd23kszl9ufd875q4ns5j0, roughly 100,000 OAG. There was no allocation in the genesis block (its reward goes to an unspendable address). Those coins were mined under the same rules as everyone else's, but you should know about them. It's about 0.01% of the 1 billion supply, but a large share of what exists today.
v0.1.2 released — https://github.com/manh923/Orange/releases/tag/v0.1.2

Upgrade recommended, especially if you are syncing a new node. No consensus change: 0.1.0, 0.1.1 and 0.1.2 nodes agree on every block.

1. Fixed: a new node could get stuck during its initial sync.
When a node synced from scratch and blocks arrived out of order at a RandomX seed switch, it could wrongly mark a valid block as invalid. After that it kept disconnecting every peer with:

Code:

dropped the exchange with ...: parent block ... is invalid

Nodes that were already in sync were not affected.
If you see that message, just upgrade and restart. 0.1.2 clears the wrong mark on startup and continues. No need to delete your data.

2. Dead connections are detected.
Nodes now ping their peers every 60 seconds and drop a peer that has not answered for 5 minutes. Before this, a node could sit on a silently dead connection and stop receiving blocks. If no new block arrives for a while, the node also asks its peers again and looks for more peers.

3. Quieter while syncing.
While a node is still catching up, it keeps 2 outbound connections, does not accept inbound ones, and does not announce its own address. It opens up normally once it has caught up.

Also: there is now a second seed node, and a public explorer at https://explorer.oagcoin.org/ (you can still run your own with --explorer).

ーーーーーーーーーーーーーーーーーーーーーーーーーーー

Should Orange have a Discord?

Right now the only official places are the GitHub repo and this thread.
I've been asked about a Discord (or something like it) and I'm not sure
it's worth it yet, so I'd like to hear what you think.

What a Discord would give us:
- quicker help for people setting up a node or mining for the first time
- a place to chat that isn't a long forum thread

What worries me:
- crypto Discords attract scammers: fake "support" DMs, fake wallet links
- someone has to moderate it, and right now that would be just me
- it splits the conversation; things said there are hard to find later

If I do make one, the rules would be simple:
- admins never DM you first and never ask for your recovery phrase
- anything I post as the developer will be signed with the block 1
  address, with the date and channel in the signed text
  (oag-wallet verify, or the Verify tab in the browser wallet)
- the invite link would be added to the README and this thread first,
  so any other "official" server is fake

Questions:
1. Would you actually use it, or is this thread enough for now?
2. Discord, or something open like Matrix?
3. Anything else you'd want from a community space?

No decision yet. I'll only set one up if there's real interest.