NervaOne version 1.3.0 released

NervaOne v1.3.0: Hard Fork Ready and Mining Affinity

NervaOne v1.3.0 is now available for Windows, Linux, macOS, and Android. It gets your node ready for Nerva’s mandatory hard fork, adds a new mining affinity option, and includes security improvements across all supported coins.

Ready for the Nerva hard fork

Nerva’s hard fork, v0.3.0.0 “Legacy Remade,” activates at block 4,320,000 (around July 21, 2026) and is mandatory. NervaOne v1.3.0 points to the new v0.3.0.0 daemon. Once you have the updated NervaOne, install it by going to Daemon Setup > Update Client Tools > Update. New users just download v1.3.0. Either way, update before the fork.

Mining affinity

NervaOne can now pin mining threads to physical CPU cores for a higher and more stable hashrate, even while you use your PC. Find the toggle under Daemon Setup > Pin mining threads to CPU cores (affinity) – on by default on desktop, off on Android. Mining with the CLI directly? Add the --mining-affinity flag to your mining command.

Security and other improvements

  • Wallet credentials and payment IDs now use a cryptographically secure random number generator
  • Password required when creating or restoring BTC-based wallets
  • Fixed precision loss in atomic-unit to amount conversion
  • Updated bundled CLI tools: Nerva v0.3.0.0, Dash v23.1.7 and Wownero v0.11.4.0

Download

Get NervaOne v1.3.0 from the downloads page or from GitHub. Each release includes a GPG-signed list of SHA256 hashes – we recommend verifying your download against it. NervaOne is open source and non-custodial; your keys never leave your device.

Nerva Legacy Remade v0.3.0.0

Nerva v0.3.0.0 “Legacy Remade”: Our First Hard Fork in Years Is Here

Today we’re releasing Nerva v0.3.0.0 “Legacy Remade”, and it carries our most significant network upgrade in a very long time. This is a mandatory hard fork. Every node operator, miner, service, and wallet user needs to update. If you run any Nerva software, this post is for you.

The short version

  • Download and install v0.3.0.0 now: https://nerva.one/#downloads
  • The fork activates at block 4,320,000, approximately July 21, 2026 (around 19:00 UTC).
  • If you have not upgraded by that block, your node stops following the real Nerva network.

Please don’t wait for the deadline. Upgrade early, confirm your node is happy, and you’re done.

1 CPU = 1 Vote

Nerva has always stood for one idea, the one Bitcoin was founded on and then drifted away from: one CPU, one vote. Mining should stay in the hands of ordinary people running ordinary CPUs. No ASIC farms, no FPGA racks, no GPU cartels, and no pools concentrating hashpower into a handful of operators. On Nerva there are no mining pools, by design. Every miner mines solo, directly on the network, on equal footing.

Keeping that promise means our Proof of Work cannot sit still, because specialized hardware and pooling schemes eventually adapt to any algorithm that never changes. It has been years since our last hard fork, and the hardware landscape has moved on. “Legacy Remade” is us moving with it: honoring what Nerva has always been while rebuilding the core that keeps it fair.

What’s new in this fork

CryptoNight-Adaptive v6, our new Proof of Work. CNA v6 uses an 8 MB memory scratchpad combined with a randomized virtual-machine program, so mining leans on memory latency and general-purpose compute, the things everyday CPUs are good at, rather than the fixed, repetitive work that specialized chips exploit. It keeps Nerva CPU-friendly and pushes back hard against ASIC and FPGA centralization.

Pool resistance, preserved. Nerva’s Proof of Work stays pool-resistant by tying mining to real blockchain data, so work can’t be neatly chopped up and farmed out to a pool the way it can on other coins. In this fork we moved that mechanism to a sliding window of recent blocks, which keeps the pool resistance fully intact while lightening what a miner needs on hand to work.

Much faster initial sync. New nodes now get caught up in minutes rather than hours. For the older, deep history of the chain the daemon trusts the checkpoints baked into the release instead of re-verifying every block from scratch, and it fully verifies the recent blocks near the tip. You get a quick start without giving up safety, and full verification is always available if you want it.

Privacy and consensus hardening. Alongside the new algorithm, this release tightens transaction validation at the consensus level, including a minimum-output rule and stricter requirements on the outputs referenced by ring signatures. These changes strengthen the privacy guarantees of the network going forward.

Closing the gap with Monero

Nerva is built on Monero’s battle-tested privacy technology, and one of our ongoing commitments is keeping our codebase current with the improvements Monero makes upstream. Over recent releases we have been steadily closing that gap, carefully porting performance, security, and stability work from Monero into Nerva while preserving the things that make Nerva its own coin, CPU-only mining and pool resistance.

This release continues that effort. The result is a stronger, more modern foundation under the hood, so Nerva benefits from the wider Monero community’s engineering without ever compromising on what makes Nerva different. Closing the gap with Monero is not a one-time task, it is a direction, and we will keep at it release after release.

We tested this thoroughly

This release did not ship on hope. It ran on public testnet ahead of the mainnet fork, and we verified the things that actually matter to users:

  • Nodes sync cleanly through the fork.
  • Mining works on the new algorithm across different CPUs and operating systems, with deterministic, matching results across machines.
  • Wallet create, restore, and transfer all function correctly before and after the fork.

What you need to do

The action is the same for everyone: replace your old binaries with v0.3.0.0 and restart. Who this applies to:

  • Miners: Update before the fork or you will be mining invalid blocks that the network rejects. Your work after block 4,320,000 only counts if you’re on v0.3.0.0.
  • Node operators: Update to stay connected to the network and to keep serving the wallets and miners that depend on you.
  • Exchanges and services: Update your daemons ahead of the fork to avoid deposit and withdrawal downtime.
  • Everyday wallet users: Update your wallet software so you can keep sending and receiving after the fork.

Using NervaOne? A new NervaOne release with the updated binaries built in is coming in the next few days. If you’d rather not wait, you can update right now: go to Daemon Setup > Update Client Tools and paste the daemon download URL for your operating system, available on the download page below. If you run the CLI daemon and wallet directly, grab the v0.3.0.0 binaries and swap them in.

Get it now

This is a big moment for Nerva, and it lands because of the people who run nodes and point their CPUs at the network. One CPU, one vote, still true, still worth defending. Upgrade, tell a fellow Nerva miner, and let’s cross the fork together.

Nerva explorer before hard fork 13

Hashrate After Hard Fork 13: Why the Number Will Drop, and Why That’s Fine

If you’re watching Nerva’s network hashrate around Hard Fork 13, brace yourself for a big drop. Right after the fork, net hashrate is going to fall sharply, we expect around a 90% drop, from 400 – 800 kH/s in the last few months to somewhere around 50 kH/s afterwards.

Before anyone panics: this is expected, it’s healthy, and it does not mean the network got weaker. Here’s exactly what’s happening and why.

The short version

Hashrate measures how many hashes the network computes per second. Hard Fork 13 replaces the mining algorithm with CryptoNight-Adaptive v6, and each hash on the new algorithm does far more work than a hash on the old one. So the same computers, working just as hard, produce far fewer hashes per second.

The number goes down because the unit changed, not because the network lost security or miners.

Why each hash is now so much heavier

Three things make a CNA v6 hash much more expensive to compute than the old algorithm:

  1. A 4x larger scratchpad. The old algorithm used a 2 MB memory buffer per hash. CNA v6 uses 8 MB. Every single hash now has to work through four times as much memory.
  2. A random program per block. Instead of one fixed calculation, each block runs a freshly generated program of hundreds of instructions, executed thousands of times. That’s a lot more computation packed into every hash.
  3. Dependent memory access. The algorithm is built so each memory step depends on the result of the one before it. Your CPU can’t run ahead or do the work in parallel, it has to wait for each step, which deliberately slows each hash down.

Add those together and a single hash takes far longer than it used to. If each hash takes roughly ten times as long, the hashes-per-second number falls by about ninety percent. Same hardware, same effort, much heavier hash.

Comparing the two numbers is apples to oranges

This is the key thing to understand: you cannot compare hashrate across two different algorithms. It’s like comparing miles per hour to laps per hour. A lower number on a longer track doesn’t mean you slowed down.

500 kH/s on the old algorithm and roughly 50 kH/s on the new one represent a similar amount of real work being done by a similar set of machines. The headline number shrank because each hash now counts for a lot more.

What about network security?

A smaller hashrate number does not make Nerva easier to attack. Security comes from how expensive it is to out-compute honest miners on the same algorithm, and CNA v6 is more expensive and more resistant to specialized hardware than the old algorithm, not less.

In fact, the new algorithm strengthens security in ways the raw number doesn’t show. The large memory requirement and random program are specifically designed to shut out ASICs, FPGAs, and GPUs, keeping mining on general-purpose CPUs where it stays widely distributed. An attacker can’t just buy specialized machines to overpower the network. They’d have to out-CPU everyone else, on an algorithm built to keep any single machine from running away with it.

What miners will notice

Your personal hashrate number will drop too, and that’s completely normal. What matters is your share of the network, and everyone’s numbers drop together, so your slice, and your rewards, stay proportional.

A few other things to expect:

  • Block times stay normal. Difficulty automatically readjusts to the lower hashrate, so blocks keep coming at about 60 seconds.
  • Un-upgraded miners fall off the real chain until they update to v0.3.0.0.

Bottom line

When you see Nerva’s hashrate drop around 90% at Hard Fork 13, that’s the algorithm change doing exactly what it’s supposed to. The number is smaller because each hash is much bigger. The network is just as secure, more resistant to specialized hardware, and still mined by everyday CPUs the way Nerva is meant to be.

Nerva has always stood for one CPU, one vote. With HF13, reality just moved a lot closer to that vision.

If you haven’t upgraded yet, do it before the fork at block 4,320,000 so you don’t miss a beat: https://nerva.one/#downloads

XeggeX website screenshot

XeggeX Is a Scam. We Got Rugged, and So Will You.

Let’s not sugarcoat this. XeggeX stole from its users, we were one of them, and anyone still trusting this exchange is walking into the same fire that already burned the rest of us. This is not a “be careful” post. This is a “stay away, full stop” post.

Here is the whole story, and what these people are doing right now to find their next victims.

This post is an updated version of our earlier XeggeX warning:

https://nerva.one/xeggex-crypto-exchange-scam/

How XeggeX robbed its users

December 2023. Nerva ($XNV) was listed on XeggeX, back when it was up and coming exchange for low-cap coins.

February 2025. XeggeX went dark. The operator, “Karl,” rolled out the oldest excuse in the book: we got hacked. The site came back weeks later, but balances were gone. In their place, IOUs for major coins and a promise that everyone would be made whole.

Then the site vanished, and so did the money. That “hack” was the cover story for a rug. Users were left with nothing but screenshots of balances they will never see again. We know, because we lost real money in it.

Call it what it is: theft.

The fake “refund” act

After laying low, the operators crawled back.

January 2026. They started stirring again in their Discord.

February 15, 2026. The old XeggeX X account announced that “refunds” were being processed. That post has since been deleted by @xeggex account.

Do not fall for it. An operation that already made everyone’s money disappear does not suddenly rediscover its conscience. The refund talk exists for one reason: to rebuild just enough hope to lure people, and fresh deposits, back in. If you actually believe you’re getting a refund from XeggeX, nothing in this post is going to save you.

What they’re doing right now: the airdrop bait

The latest hustle is pure recruitment. XeggeX is spamming “airdrop” hype and telling people to hand over their Solana wallet addresses:

  • “drop your solana address, check the wallet later”
  • “Show me your solana addresses. ITS AIRDROP SEASON.”

There is no airdrop. Begging strangers for wallet addresses is how scammers build victim lists and steer people to wallet-draining sites and fake “claim” pages, where one signature empties your wallet. A real exchange does not run its business panhandling for wallet addresses in X replies.

And watch what they do to anyone who warns you: when we called them out, XeggeX blocked us. That’s the tell. Scammers block the people telling the truth because honesty kills their recruitment. The block isn’t defensive, it’s part of the con.

So burn this in: never send funds to XeggeX, never give them your wallet address, and never connect a wallet, install any app from them or sign anything for a XeggeX “airdrop.” The airdrop is the hook. You are the fish.

People are STILL losing funds

This isn’t ancient history that got cleaned up. As recently as May 24, 2026, users were publicly begging XeggeX for their money:

  • “I buy xeggex coins but my xeggex coins not showing”
  • “My fund not showing”

Months after the “refunds” supposedly started, real people are still locked out of real funds. That’s the truth sitting underneath all the airdrop noise.

AnonEx: XeggeX’s second act, admitted out loud

AnonEx tried to wave us off, posted from their own account: “We have no affiliation with Xeggex or the previous team. We only purchased the software from Xeggex.”

Read that again, because they admitted it themselves. They bought their exchange software directly from XeggeX, the operation that stole over $10 million from its users. Our reply was the only question that matters: why would anyone buy their platform from a known, confirmed scammer?

Then AnonEx vanished, right on cue:

  • Its official X account, @anonexofficial, no longer exists.
  • Its website, anonex.io, is dead. The domain doesn’t even resolve.

Same code, same crew, same rug. If you had anything on AnonEx, it’s gone. This is what happens every single time: when a “new” exchange proudly runs a known scammer’s code, it isn’t a new exchange. It’s the next rug.

A warning for every past XeggeX user: do not log into xeggex.com

Here’s something every former XeggeX user needs to hear. Alongside those code-sale messages, a serious warning has been circulating: that the current xeggex.com is now a honeypot set up to harvest logins, with people urged not to enter their credentials and to change any reused passwords.

We can’t independently confirm who controls that domain today, but the precaution costs you nothing and the downside of ignoring it is severe:

  • Do not enter your login on xeggex.com.
  • If you ever used XeggeX and reused that email and password anywhere else, change those passwords now, especially your email, other exchanges, and anything financial.

They already took people’s funds. Don’t hand them your credentials too.

Know the playbook

XeggeX and AnonEx ran the same script, and so do most exchange scams. If you see these signs, walk away:

  • A convenient “hack” that just happens to wipe user balances, followed by IOUs and vague promises.
  • Going dark, then reappearing with fresh promises of refunds or rewards.
  • “Airdrops” that want your wallet address, a wallet connection, or a signature.
  • Buying or running a known scammer’s code and branding it a “new” exchange.
  • Blocking and silencing critics instead of answering them.
  • Anonymous operators with zero accountability when the money disappears.

Hold your own keys. Only use exchanges with a real, verifiable track record, and never leave more on any exchange than you’re actively trading. If a “gift” needs your wallet or a signature, it’s a robbery with a bow on it.

We’re not letting this go

We got rugged by XeggeX, and we’re not going to sit quietly while they and their spinoffs line up the next round of victims. We warned everyone about the airdrop bait, we’ve documented AnonEx, and we’ll keep publishing every scam we uncover. These people count on short memories and silenced critics. They’re going to get neither from us.

If XeggeX, AnonEx, or any operation like them burned you too, speak up and share it. Come tell us:

The more we document, the harder these scams are to pull off, and the fewer people they get to rob.

Protect your keys. Trust no exchange. And do not feed these scammers.

Hard fork 13 sync speed improvements

Hard Fork 13: A Fairer Algorithm, and Faster Sync

A while back we said sync speed was “only step 1” and that bigger improvements were coming. This is that step. Alongside Hard Fork 13, the upcoming release brings a sync experience that turns days into hours, plus the biggest change to Nerva’s mining algorithm in many years.

We heard you. Sync is now hours, not days

In v0.2.2.0, a full sync from scratch took around 20 hours. With the changes in this upcoming release, the same sync completes in about 71 minutes on our reference machine (a high-end AMD Ryzen 9 7950X).

That’s roughly a 17× improvement. Your exact time will depend on your CPU, disk, and network, but the shape of the improvement holds on any machine.

Where the time goes (and why this works)

The single biggest cost of syncing a Proof-of-Work chain isn’t downloading blocks but recomputing the Proof-of-Work hash for every block to re-verify it. On a chain of 4.28M blocks, almost all of that work re-verifies ancient, long-settled history. Nerva is heavier here than Monero by design: its algorithm derives each block’s hash partly from data scattered across the chain’s own history, so verifying a block means random lookups into many older blocks. That’s what makes Nerva pool-resistant but it also means the work grows as the chain does, since those reads spill out of fast CPU cache.

The last under 1% of the chain took nearly a third of the total time because those are the only blocks whose PoW was fully recomputed. Skip that redundant work on settled history and sync collapses from many hours to a fraction of the time.

That’s exactly what this release does. For blocks below a built-in, hardcoded checkpoint height, the daemon skips recomputing PoW and relies on the checkpoint instead. Everything else: difficulty, timestamps, transaction inputs and outputs, and the chain-linking between blocks is still fully validated for every single block.

“But I want to verify everything myself”

You can and it’s one flag.

The fast path is on by default because it gives the best experience for the vast majority of users. If you’d rather verify every block’s Proof-of-Work from genesis to tip, start the daemon with:

nervad --fast-block-sync 0

This re-runs PoW for the entire chain using the traditional, verify-everything sync. It takes considerably longer (the PoW work is the whole point), but the choice is yours. Fast by default, fully verifiable on demand.

Is the fast path safe?

Yes and the reason is the way a blockchain is built.

The release will ship with hardcoded checkpoints: known-good hashes of specific historical blocks. Because each block’s hash depends on its parent, which depends on its parent, all the way down, a checkpoint cryptographically pins the entire history beneath it.

If anyone tried to feed your node a doctored historical chain, altering even one old block would change every hash above it, and the chain would no longer match the checkpoint. Your node would reject it. The worst an attacker could do is make a not-yet-synced node stall, never accept a fake chain. The block hash is always computed independently by your own node; it’s never trusted from the network.

In short: the fast path trusts the software you’re running, not the peers you’re downloading from, the same trust you already place in the daemon binary.

Hard Fork 13: a fairer algorithm

Sync speed is half the story. HF13 also introduces CryptoNight-Adaptive v6, a reworked Proof-of-Work designed around a simple principle: 1 CPU = 1 Vote.

The new algorithm is memory-bound. Instead of rewarding raw core speed where high-end chips and specialized hardware pull far ahead, it gates each hash on memory latency, which is far more uniform across devices. The result is a per-core hash rate that drifts toward the same number whether you’re on a laptop or a large desktop, compressing the gap between small miners and big ones.

Three design choices make this work:

  • A random program every block. Each block runs a unique, unpredictable sequence of operations derived from the chain itself. This defeats fixed-function ASIC circuits. There’s no single pipeline to bake into silicon.
  • A large scratchpad. An 8 MB working area per hash starves GPUs of the occupancy they need to excel, while staying practical on ordinary CPUs.
  • A chain-rooted seed. The per-block program depends on real data from the blockchain itself, which makes centralized pool mining architecturally difficult, a core part of Nerva’s pool-resistant design.

Together they strengthen Nerva’s promise of CPU mining: open to anyone with an everyday computer, hostile to specialized and centralized hardware.

Keeping the new algorithm fast to sync

A memory-bound algorithm that reads from the blockchain could, in principle, make syncing slower as the chain grows. We designed around that with a sliding window.

When verifying the new algorithm, about 95% of the historical reads are drawn from the most recent ~100,000 blocks, roughly 5.6 MB of data that fits comfortably in a modern CPU’s L3 cache. The remaining ~5% reach into the full history to preserve pool resistance. The effect: verification stays cache-friendly and fast no matter how long the chain gets, so HF13’s stronger algorithm doesn’t come at the cost of sync time.

The bottom line

Hard Fork 13 will bring two things that matter to very different users:

  • New users get up and running in a few hours, not days.
  • Everyone gets a fairer, more decentralized algorithm, memory-bound, ASIC- and GPU-resistant, that keeps existing pool-resistance without giving up the option to fully validate every block.

Fast by default. Fully verifiable on demand. Fairer for everyone who mines.

That’s what’s coming in Hard Fork 13. Testnet soon.

Nerva CLI v0.2.3.0

Nerva v0.2.3.0: Legacy Reborn, Point Release 3

Overview

Nerva core v0.2.3.0 is a focused release that resolves a sync-halting crash affecting all users syncing from genesis, delivers measurable performance gains across both P2P and QuickSync, and extends hardware acceleration to ARM64 platforms. If you are syncing a fresh node without QuickSync, this upgrade is essential.

Sync Crash Fix (HF7 / CNA v2 Boundary)

Users syncing from block 0 encountered a fatal crash at block 173,500, the point where the CNA v2 proof-of-work algorithm activates at hard fork 7. The block cache was opening a read-only LMDB transaction that could not see blocks still pending in the current uncommitted write batch, resulting in an MDB_NOTFOUND error, peer disconnection, and a sync loop that could not progress past that boundary. The fix caps the adaptive sync batch size at 256 blocks, guaranteeing that all blocks needed for PoW lookups are committed and visible before the cache reads them.

Performance: Boost 1.89 Mutex Fix

A regression introduced with Boost 1.89 caused sleep_for(milliseconds(0), previously a no-op, to execute a real cond_timedwait costing approximately 1ms per call. Because CRITICAL_REGION_LOCAL invokes this on every mutex acquisition, the penalty accumulated across all lock-heavy code paths.

The fix removes the sleep from the hot path entirely, in line with upstream Monero. Measured impact on Windows:

  • QuickSync: ~10% faster
  • P2P sync: ~6% faster overall, with up to 16% improvement in the post-HF12 range (blocks 930k–1.2M) where lock contention is highest
  • Wallet generation: significantly faster (expanding the default subaddress lookahead previously triggered ~40,000 lock acquisitions, adding ~40 seconds of unnecessary sleeping)

ARM64 Hardware AES Acceleration

Hardware AES intrinsics are now enabled for 64-bit ARM targets, including Apple Silicon (M-series) and ARM64 Linux devices. This brings ARM performance in line with x86_64 for the cryptographic operations at the core of NERVA’s PoW.

Download & Upgrade

The sync crash fix makes this a required upgrade for anyone running a fresh node who wants to sync without QuickSync. All other users are encouraged to upgrade for the performance and wallet improvements.

🔗 https://nerva.one/#downloads

🔗 https://github.com/nerva-project/nerva/releases/tag/v0.2.3.0