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

[oag-manh]

v0.1.7 released

https://github.com/manh923/Orange/releases/tag/v0.1.7

This is an optional update. There are no consensus changes, so 0.1.2 and later keep working on the same chain. Upgrade when convenient.

Explorer: who is mining
explorer.oagcoin.org/stats now shows who mined the last 100 blocks: each address, how many blocks, and its share.
If a single address has mined more than half of them, the page says so plainly. Whoever has more than half of the hashrate can undo recent blocks, including their own payments, so when that warning is up, wait for more confirmations than usual on large amounts. Nobody is accusing anyone; it is just something anyone receiving coins should be able to see.

Node: clearer reorg messages
When the node switches to another branch, it now logs every block it dropped and adopted, with height and hash, instead of only the counts:

Code:

[check] reorg  -1 +2  height 14052
[check]   dropped 14051  9c41d07e
[check]   adopted 14051  5b2e88a1
[check]   adopted 14052  e07f3c52

A 1-block reorg like this is normal with 60-second blocks: two miners found a block at almost the same time, and the chain with more work won. You can look up the hashes in the explorer.

Difficulty adjustment
Nothing changes. The LWMA window (N = 90) is now documented as final. It has handled a 4x jump in hashrate and the drop back within hours, as designed.

Upgrading
Stop the node, replace oag-node and oag-wallet with the new files, and start it again. Your data folder is kept as it is; no resync. Check the download against the .sha256 file next to it.

Questions and chat: Discord

[cryptomaxsun]

Code:

[check] switched the RandomX seed to block 9469e231 at height 14336
[check] switched the RandomX seed to block fc419cb9 at height 10240
[check] switched the RandomX seed to block 9469e231 at height 14336
[check] switched the RandomX seed to block fc419cb9 at height 10240
[check] switched the RandomX seed to block 9469e231 at height 14336
[check] switched the RandomX seed to block fc419cb9 at height 10240
[check] switched the RandomX seed to block 9469e231 at height 14336
[check] switched the RandomX seed to block fc419cb9 at height 10240
[check] switched the RandomX seed to block 9469e231 at height 14336
[sync] headers +2 (2 total)  chain known to height 15398
[check] switched the RandomX seed to block fc419cb9 at height 10240
[check] switched the RandomX seed to block 9469e231 at height 14336
[check] switched the RandomX seed to block fc419cb9 at height 10240
[check] switched the RandomX seed to block 9469e231 at height 14336
[check] switched the RandomX seed to block fc419cb9 at height 10240

It's not syncing. I'm on the latest version.

And what are the future plans for the coin's development?
Exchanges?

[oag-manh]

It's not syncing. I'm on the latest version.

And what are the future plans for the coin's development?
Exchanges?

Thanks for the log.

The sync stall is fixed in v0.2.0, released just now:
https://github.com/manh923/Orange/releases/tag/v0.2.0

0.1.7 had a bug where restarting the node during the initial sync could leave gaps in the downloaded blocks, and it never went back to fetch them, so it stopped making progress. 0.2.0 fetches them.
You don't need to delete anything. Stop the node, replace oag-node and oag-wallet with the new files, and start it again. It will continue from where it is.

The repeated "switched the RandomX seed" lines are a separate issue. Around height 14400 the node rebuilds its RandomX cache more often than it needs to, which slows the sync down but doesn't stop it. I've found the cause and it will be fixed in a later release.

About the future: I'm not planning to list OAG on exchanges or to run one myself. Anyone is free to list it.

[oag-manh]

Orange v0.3.0 released, and OAG can now be mined with XMRig

1. oag-node v0.3.0
https://github.com/manh923/Orange/releases/tag/v0.3.0

• --stratum: the node serves work to external miners (default 127.0.0.1:1919).
• --pool: the node runs as a PPLNS pool with its own key and pays miners once rewards mature (120 blocks). Defaults: 0% fee, 1 OAG minimum payout, payouts every 10 minutes. The fee is set with --pool-fee and --pool-fee-address, and a status page opens on port 8000.
• There is no consensus change. 0.3.0 works with 0.2.x nodes.

I am not running a public pool myself. Anyone is free to run one.

2. XMRig for OAG (v6.26.0-oag.1)
https://github.com/manh923/xmrig-for-oag/releases/tag/v6.26.0-oag.1
Stock XMRig cannot mine OAG, because the OAG block header has a different layout from Monero's. This fork of XMRig 6.26.0 adds the algorithm rx/oag. Every build was checked against real mainnet blocks before release. Builds are available for Windows x64 and Linux x64/arm64 (static).

Code:

oag-node run --network mainnet --stratum
xmrig -o 127.0.0.1:1919 -u <your OAG address> -a rx/oag

• Start XMRig after the node has finished syncing.
• CPU only.
• The donation is XMRig's default 1%: about 1 minute in 100 is spent mining Monero for the XMRig authors.
• Windows Defender may flag xmrig.exe as Trojan:Win32/Wacatac.B!ml. This is a false positive that affects most XMRig builds. The source is public (GPL-3.0), and SHA256SUMS is attached to the release.
• Keep port 1919 on localhost or your LAN. Anyone who can reach it can mine through your node.

Protocol spec for miner developers: docs/STRATUM.md

[oag-manh]

Orange v0.4.0: soft fork at block 40,000 (miners, please update)
https://github.com/manh923/Orange/releases/tag/v0.4.0

What changes
From block 40,000 (around October 15 UTC, depending on hashrate), nodes enforce relative locktime: the sequence field with BIP68 semantics, like Bitcoin's CSV. A version 2 transaction can say "this input can only be spent N blocks (or N × 512 seconds) after the output it spends was confirmed". Payment channels and safer atomic swap refunds need this. OAG has no scripts, so channels are built with adaptor signatures plus this timelock.

The rule only applies to version 2 transactions. Version 1 transactions, which is what every current wallet makes, are not affected. The semantics were already fixed in the spec (§7.5) at launch; this release only starts enforcing them. It was proposed and voted on in our Discord.

Who needs to update

• Miners and pool operators: required before block 40,000. After that height, upgraded nodes reject a block that breaks the new rule, so an old node can mine a block that gets thrown away.
• If you mine through someone else's pool, the pool operator updates. XMRig itself does not change.
• Other node operators: recommended.
• Wallet users: nothing to do.

Upgrading
Stop the node, replace oag-node and oag-wallet, start it again. Your data is kept; no resync. 0.4.0 works with 0.2.x and 0.3.x peers.

[oag-manh]

Orange (OAG) - Day 17 report

Orange has been running for 17 days. Blocks keep coming about once a minute.

Chain
- Height: 23,743 (16.8 days). We passed block 20,000 on Oct 2.
- Average block time: 61.0 s (target 60 s)
- Hashrate: 153.89 kH/s over the last hour, 138.88 kH/s over the last 24 hours
  (Day 10: 2.29 kH/s and 3.52 kH/s - about 40 times more in one week)
- Next difficulty: 9,137,918 (Day 10: 141,731)

Hashrate by day
- Sep 27: 3.12 kH/s
- Sep 28: 4.25 kH/s
- Sep 29: 15.83 kH/s
- Sep 30: 24.86 kH/s
- Oct 1: 23.45 kH/s
- Oct 2: 28.10 kH/s
- Oct 3: 115.74 kH/s
- Oct 4 so far: 158.48 kH/s

People
- Addresses holding coins: 39 (Day 10: 21)
- Addresses that have mined a block: 30 (Day 10: 14)
- Addresses that mined in the last 7 days: 22
- Transactions (not counting mining rewards): 407 (Day 10: 34)
- Coins in circulation: 237,430 OAG
- There are now two pools. Besides mine, someone else is running their own
  pool with oag-node --pool and paying out to its miners every ~10 blocks.

Mining concentration (last 100 blocks)
- The largest miner found 47% of them. On Oct 3 it was 61%.
- Anyone with more than half of the hashrate can undo recent blocks.
  For large amounts, please wait for more confirmations than usual.
- Every new miner, solo or in a pool, makes this number go down.

Distribution
- The largest address (31.7%) is not mine. It belongs to drywall777,
  who has mined steadily since Sep 24 and also received my thank-you gift.
- My address is now about 28.7%. On Day 10 it was 49.2%.
- Correction to Day 10: I wrote that I had practically stopped mining.
  I still mine a little: 20 blocks since then, out of about 9,700 (0.2%).
- Top 10 addresses hold 94.1%. Still concentrated, but falling.
Check it yourself any time: https://explorer.oagcoin.org/stats

Released this week
- 0.1.7: /stats shows who mined the last 100 blocks; reorgs are logged in detail
- 0.2.0 / 0.2.1: fixed a sync stall after restarting during the initial sync
- 0.3.0: --stratum lets external miners (XMRig for OAG, algo rx/oag) mine;
  --pool runs the node as a PPLNS pool (0% fee, 1 OAG minimum payout)
- 0.4.0: soft fork at block 40,000 - relative locktime (BIP68-style)
Downloads: https://github.com/manh923/Orange/releases

Please update before block 40,000
- Block 40,000 is about 16,000 blocks away, around Oct 15-16 UTC.
- Miners and pool operators: please run 0.4.0 or later by then.
- Today's wallets make version 1 transactions, which the soft fork does not touch.

Other news
- I asked for a SLIP-0044 coin type (number 1033, PR #2062). It is not merged yet.

Questions and chat: https://discord.gg/72KWbXkn86

[oag-manh]

**Orange v0.4.1**
https://github.com/manh923/Orange/releases/tag/v0.4.1

**Changes**
- Fixed: a node could keep dialling its own address ("detected a connection to ourselves" in the log), even with --external-addr. It now drops its own address from the address book and never dials it again. Thanks to Jeeves for the report.
- Added a second mainnet seed: oagnode.vslabs.co.in. Thanks to gvsa (PR #1).

**Who needs to update**
Optional. The soft fork rules at block 40,000 are the same as in 0.4.0, so 0.4.0 nodes are fine. If you are still on 0.3.x or older, update before block 40,000 (around October 15-16 UTC).

**Upgrading**
Stop the node, replace oag-node and oag-wallet, start it again. Your data is kept; no resync.

[oag-manh]

Orange (OAG) v0.4.3 — reorg fix, please update

What was wrong
If a block contained a transaction that spent an output created earlier in the same block (e.g. spending your change right away), nodes could not undo that block during a reorg. The node got stuck on its current branch and could never reorganize below that block, which could leave the network split.

What changed
Undo now correctly skips outputs that were both created and spent inside the same block.

• No consensus rule changes — this is not a hard fork. Old and new nodes stay compatible.
• No database migration. Undo data written by older versions is handled correctly.
• New regression tests cover this case on both the in-memory and on-disk (redb) stores.

Who should update
Everyone running a node, especially seed nodes, pools and miners.

Download
https://github.com/manh923/Orange/releases/tag/v0.4.3
Windows / Linux x86_64 / Linux aarch64 (Raspberry Pi) binaries with SHA-256 checksums. macOS: build from source (see README).

[oag-manh]

Orange (OAG) — Day 24 update

Block 1 was mined on 2026-09-17. Here is where the network stood on day 24 (2026-10-10 UTC).

Network (day 24)

• Blocks mined that day: 1,386 (target is 1,440 at 60 s)
• Average hashrate: 38.8 kH/s
• Addresses that mined that day: 14
• Addresses holding coins: 52
• Transactions that day: 95

First community pool
Orange Pool, run independently by gold-atom, found its first block at height 33,069 and made its first payouts the same day.

• Endpoint: mine.orange.gen.nz:1920 — 1% fee, PPLNS, 1 OAG minimum payout
• Site and forum: https://orange.gen.nz/
• It is now listed in the README under "Community pools". A listing is not an endorsement — check the operator's terms before connecting.

Please spread your hashrate. No single pool or miner should hold a majority.

Soft fork at height 40,000 — update your node
Relative locktime is enforced from height 40,000 (expected around 2026-10-15 UTC). Nodes and miners must run v0.4.0 or later; v0.4.3 is recommended because it also fixes a reorg bug.
https://github.com/manh923/Orange/releases/tag/v0.4.3

What comes next (planned, not released)

• Commitment outputs: a zero-value, unspendable output carrying 2–40 bytes, for timestamping hashes (release checksums, key-rotation notices, pool ledgers). Proposed in Issue #2.
• Activation by miner signaling: from the next soft fork on, new rules activate once at least 2/3 of the last 1,440 blocks (960 blocks) signal readiness, instead of at a fixed height. Details will be published with the release.

Do not send coins to unknown address versions before a soft fork activates. Old nodes treat them as anyone-can-spend.

Source: https://github.com/manh923/Orange


Orange (OAG) v0.5.0 — miner-signalled soft fork, network hardening

Please update. Miners and pool operators especially.

1. Soft fork, activated by miners (BIP9 style)
From now on, soft forks activate only after miners signal readiness in the block header.

• Signal: header version top bits 001 with bit 1 set (0x20000002). Nodes running 0.5.0 put it in their block templates automatically.
• Counting starts at height 40,320, in periods of 1,440 blocks (about a day).
• If 960 of 1,440 blocks (2/3) signal, the fork locks in. One more period later it becomes active.
• If it never reaches 2/3, it fails at height 565,920 (about a year).

Old nodes accept signalling blocks, so nothing splits while counting.

Pool operators: use the version from the node's template as is. If your software sets the header version itself, your blocks will not signal. You can check the count with getinfo (softfork.signalled / softfork.elapsed) or on the explorer's stats page.

What the fork turns on

• Commitment outputs (version 3): an output carrying 0 OAG and 2–40 bytes, which nobody can spend and which never enters the UTXO set. Use it to timestamp a hash. Wallet: oag-wallet commit <hex> (refused until the fork is active).
  
• txid malleability fix: up to 0.4, appending a 0x00 byte to a 64-byte signature changed the txid while the transaction stayed valid. 0.5.0 no longer relays that form, and after activation it is invalid (same as BIP341).
  

2. Network hardening

• 60-second handshake timeout; 1 KiB payload limit until the handshake completes.
• Inbound connections capped at 117, and 4 per IP address.
• The listener no longer stops when accept() fails (e.g. out of file descriptors).
• Per-peer header rate limit; peers sending invalid headers are banned for 24 hours.
• Header branches far lighter than the best chain are kept in memory instead of being written to disk (same idea as Bitcoin Core's anti-DoS threshold). There is still no reorg depth limit.

Download
https://github.com/manh923/Orange/releases/tag/v0.5.0

Specification: docs/SPEC.md §7.7, §10.5, §10.9.