Orange (OAG): the token, in plain words

What is OAG?
Why miners and holders like it
Latest Orange news
Orange pool opens on port 33344
The oag engine went in behind the existing multi-coin stack: miners log in with an oag1 address, the pool validates every share locally with the same stock RandomX the chain uses (both mainnet test vectors from the project's stratum spec reproduce byte-for-byte), and only block candidates travel to the node's own solo stratum. Payouts start as a dry run — shares, blocks and balances count in real time while the transfer path proves itself.
source →How-to-mine page, with the xmrig-for-oag build
The guide carries ready-made command lines around xmrig-for-oag v6.26.0-oag.1 — stock XMRig does not know rx/oag, its nonce offset and its big-endian hit rule — plus the port table, the payout fine print (1% fee, 1 OAG minimum, 120-block maturity) and the address shape rules that keep a worker name from turning into a lost payout.
source →The stratum spec, in full
The project documents its mining dialect down to test vectors: the blob is the 100-byte header, the miner writes a u32 LE nonce at offset 92 and hashes the whole thing with seed_hash as the verbatim RandomX key; a hit is the first eight bytes of the digest read big-endian, at or below the target. Two real mainnet blocks are printed with their pow hashes so any implementation can prove itself.
source →Node and wallet CLI reference
Every command and RPC in one page: oag-node run with --stratum, --rpc and --listen, the cookie-auth HTTP RPC (getblockcount, getblockhash, getblockheader…), and oag-wallet for new/address/send — the wallet deliberately reads its passphrase from a file, never the command line.
source →Releases, with checksums
The v0.4.0 tarball carries the node and the wallet for Linux x86_64 and arm64, each with a .sha256 file to verify before anything is unpacked — the pool's own node setup checks the sum and refuses to proceed on a mismatch.
source →Watch the chain, check the payments
The project's explorer tracks blocks, difficulty and addresses — every payout the pool sends appears there as an ordinary transaction to an oag1 address, transaction id included.
source →