Bitcoin Forum
September 25, 2026, 03:07:26 PM *
News: Latest Bitcoin Core release: 31.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: [ANN] Orange (OAG) | RandomX CPU-only | No premine | Solo mining | Rust  (Read 258 times)
oag-manh (OP)
Newbie
*
Offline

Activity: 11
Merit: 0


View Profile
September 24, 2026, 12:15:59 PM
Last edit: Today at 01:57:01 AM by oag-manh
 #1

Orange (OAG)

  • 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.

A small CPU-mined UTXO coin. RandomX proof of work, written in Rust.

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 very few participants, and I am looking for people who will mine it and run nodes.

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.

Specifications
Proof of workRandomX (CPU)
AccountingUTXO
SignaturesSchnorr / BIP340 (secp256k1)
Block time60 seconds
DifficultyLWMA, every block
Block reward10 OAG, flat, no halving
Max supply1,000,000,000 OAG (emission ends after about 190 years)
Premine0 (the 10 OAG in the genesis block is unspendable)
Genesis2026-09-01 00:00 UTC
P2P port9444

Solo mining only
There is no pool protocol. 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 is also someone keeping the network alive.

How to start (Windows)
1. Download orange-windows-x86_64.zip from the latest release and unpack it.
2. Check the file (compare with 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. Each thread needs 256 MB of RAM.
Code:
.\oag-node.exe run --network mainnet --mine --payout <your address> --mining-threads 0

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

You do not have to mine. Running oag-node run --network mainnet without --mine validates and relays blocks, and that already helps.

Links

There is no public explorer. Run your own: the node has one built in. Add --explorer to the command you already run (do not start a second node):
Code:
.\oag-node.exe run --network mainnet --mine --payout <your address> --explorer
The first time, it builds an index first. Wait for "explorer open at http://127.0.0.1:8080/", then open that address in a browser on the same computer. Search for your payout address; each row marked "mined" is a block you found.

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.

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.
I am in Japan (UTC+9), so replies may take up to a day.

Add --explorer to the command you already run (do not start a second node):
Code:
.\oag-node.exe run --network mainnet --mine --payout <your address> --explorer

Looking for seed node operators

New nodes find their first peers through a DNS seed. Right now there is only one seed node, and it is mine. 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 to the internet, post your IP here (or in a GitHub issue). After checking that 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 of your own, 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 on my domain.

Please note: a seed's IP address is public by nature, since anyone can look it up. There is no reward for this; it is purely volunteering.
oag-manh (OP)
Newbie
*
Offline

Activity: 11
Merit: 0


View Profile
September 24, 2026, 01:27:04 PM
 #2

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
Newbie
*
Offline

Activity: 4
Merit: 0


View Profile
September 24, 2026, 11:47:41 PM
 #3

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 (OP)
Newbie
*
Offline

Activity: 11
Merit: 0


View Profile
Today at 01:32:33 AM
Last edit: Today at 07:50:55 AM by Welsh
 #4

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
Newbie
*
Offline

Activity: 7
Merit: 0


View Profile
Today at 02:12:05 AM
 #5

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 (OP)
Newbie
*
Offline

Activity: 11
Merit: 0


View Profile
Today at 03:12:29 AM
 #6

Quote from: shyeah
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
Newbie
*
Offline

Activity: 4
Merit: 0


View Profile
Today at 06:17:02 AM
 #7

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 (OP)
Newbie
*
Offline

Activity: 11
Merit: 0


View Profile
Today at 07:09:36 AM
 #8

Quote from: drywall777
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
Newbie
*
Offline

Activity: 395
Merit: 0


View Profile
Today at 07:11:17 AM
 #9

PoW is not a RandomX, you lie, hashrate is to low for RandomX.
oag-manh (OP)
Newbie
*
Offline

Activity: 11
Merit: 0


View Profile
Today at 07:21:03 AM
 #10


Quote from: BoozyTalking
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 (OP)
Newbie
*
Offline

Activity: 11
Merit: 0


View Profile
Today at 07:53:41 AM
 #11

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.

Mode1 thread6 threads (0.1.0)6 threads (0.1.1)
light256 MB1.5 GB1.5 GB
fast2 GB12 GB2 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
Newbie
*
Offline

Activity: 395
Merit: 0


View Profile
Today at 09:32:24 AM
 #12

Now is much better.
oag-manh (OP)
Newbie
*
Offline

Activity: 11
Merit: 0


View Profile
Today at 09:35:52 AM
 #13

thank you!
AliErkic
Jr. Member
*
Offline

Activity: 154
Merit: 2

SIG-909C7044FF


View Profile
Today at 09:54:16 AM
 #14

Nice project, Sir!

xrp shitcoin is SCAM!  **  Get out!  **  Don't get scammed by Ripple Labs and scammer Garlinghouse ** xrp shitcoin is SCAM!  **  Get out ASAP!!
oag-manh (OP)
Newbie
*
Offline

Activity: 11
Merit: 0


View Profile
Today at 09:57:48 AM
 #15

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!
oag-manh (OP)
Newbie
*
Offline

Activity: 11
Merit: 0


View Profile
Today at 10:10:59 AM
 #16

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.
Cashi
Full Member
***
Offline

Activity: 458
Merit: 139


View Profile
Today at 10:34:45 AM
 #17

Good project, Sir

Smiley Smiley
Sergick2023
Newbie
*
Offline

Activity: 22
Merit: 0


View Profile
Today at 10:48:04 AM
Last edit: Today at 02:06:49 PM by Welsh
 #18

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


This right way?
oag-manh (OP)
Newbie
*
Offline

Activity: 11
Merit: 0


View Profile
Today at 10:56:46 AM
Last edit: Today at 02:08:06 PM by Welsh
 #19

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
Newbie
*
Offline

Activity: 4
Merit: 0


View Profile
Today at 02:28:35 PM
 #20

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.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!