[ANN][VOID] VoidCoin revived-preserved, v1.1.0 merge-mining with Bitcoin SHA256

[solarsurfer]

VoidCoin revived – source preserved, v1.1.0 merge-mining (auxpow) with Bitcoin from block 56,500


Hi all,

I'm Andy from Shears Mining https://sha256-mining.shears.co.uk, a small solo/merge-mining pool for home SHA-256 miners.

As some of you will have noticed, the VoidHash-Crypto GitHub repository has gone (404), and the developers can no longer be reached: emails bounce. We've been running VoidCoin nodes and mining the chain, and we didn't want the coin to disappear with the repo. So:

1. The source is preserved. We had a full clone of the original repository, and it's now public, unchanged, with all of the original developers' commits and release tags (v1.0.0 - v1.0.5):
https://github.com/Shears-Mining/voidcoin

All credit for VoidCoin goes to the original VoidHash-Crypto team, and VoidCoin itself is built on Kvanta5-Core: the quantum-resistant ML-DSA-87 / P2QR code is the work of the Kvanta5 developers.

2. VoidCoin Core v1.1.0 is out, adding merge-mining (AuxPoW) with Bitcoin from block 56,500. Bitcoin miners will be able to mine VOID with the same work at no extra cost, which brings far more hashrate to secure the chain. The AuxPoW code is ported from Namecoin Core.
- Chain ID 0x56. Normal (non-merge-mined) blocks stay valid, so direct miners carry on as before.
- Nothing else changes: 50 VOID reward, VCIP-2 bounty blocks, 0.1 VOID tail, 1-minute blocks, P2QR quantum-resistant addresses.
- Tested: v1.1.0 re-validated the whole live chain (identical to v1.0.5), plus 22 merge-mining checks on a test chain.
- Downloads (Linux, and a Windows wallet) with checksums: https://github.com/Shears-Mining/voidcoin/releases/tag/v1.1.0
- Pool operators: doc/merge-mining.md in the repo.

⚠️ IMPORTANT: v1.0.x nodes will stop following the chain at block 56,500 (the chain is at about 53,800 now). If you run a VoidCoin node or wallet, please upgrade before then. Your data folder and wallet carry over unchanged. Back up your wallet first anyway.

Public node: addnode=stratum.shears.co.uk:9779

To be open about where things stand: right now our pool is the only miner and our nodes are the only ones online, so more nodes and miners are very welcome. If you're an original developer or long-time holder and you're still around, please get in touch here, or open an issue on GitHub. We'd be glad to hand things back or work together.

Thanks,
Andy - Shears Mining

Original (locked) announcement: https://bitcointalk.org/index.php?topic=5587143.0

[lightbit]

Really appreciate seeing someone step in to preserve a project rather than letting it disappear when the original developers become inactive.

Keeping the original commit history intact and introducing AuxPoW while maintaining compatibility with existing direct miners is an interesting approach.

One thing I'm curious about: since Shears Mining is currently the only active miner, do you have plans to attract independent pool operators and node runners ahead of block 56,500?

The post-quantum address support combined with Bitcoin merge-mining makes VOID worth following. Would be great to see the network become more decentralised as the revival progresses.

[solarsurfer]

Really appreciate seeing someone step in to preserve a project rather than letting it disappear when the original developers become inactive.

Keeping the original commit history intact and introducing AuxPoW while maintaining compatibility with existing direct miners is an interesting approach.

One thing I'm curious about: since Shears Mining is currently the only active miner, do you have plans to attract independent pool operators and node runners ahead of block 56,500?

The post-quantum address support combined with Bitcoin merge-mining makes VOID worth following. Would be great to see the network become more decentralised as the revival progresses.

Thanks, that's exactly the goal. A revival run by one pool isn't a revival yet, so here's the plan for before and after block 56,500:

- Time to upgrade: we've paused our own VOID mining so the chain doesn't race to 56,500. The switch-over will land around mid-November, giving anyone who runs a node or wallet time to move to v1.1.0. The exact date depends only on when mining resumes, and I'll post a heads-up here a few days before.

- Nodes: our public node is open now (addnode=stratum.shears.co.uk:9779). Anyone running v1.1.0, even a small VPS or a Raspberry Pi-class box, makes the network more robust. Post your node here and I'll add it to the README as a seed.

- Pool operators: doc/merge-mining.md in the repo has everything needed (chain ID 0x56, the standard createauxblock/submitauxblock RPCs). Any pool that already merge-mines Namecoin-style coins can add VOID as one more aux chain. I'll contact some of the smaller merge-mining pools directly, and I'm happy to help anyone test against our node before the switch.

- Miners: once merge-mining is live, VOID will be free to merge-mine on our pool for a month, so lots of independent Bitcoin miners will be finding VOID blocks to their own addresses, not ours.

- Visibility: we'll list VOID on MiningPoolStats as soon as a second pool is mining it.

If any of the original developers or Kvanta5 folks want to be involved, the door is open. The more hands on this, the better.

Andy - Shears Mining

[Akka 007]

Really appreciate seeing someone step in to preserve a project rather than letting it disappear when the original developers become inactive. Keeping the original commit history intact and introducing AuxPoW while maintaining compatibility with existing direct miners is an interesting approach. The post-quantum address support combined with Bitcoin merge-mining makes VOID worth following. Would be great to see the network become more decentralised as the revival progresses.

[solarsurfer]

VoidCoin block explorer is live

https://void-explorer.shears.co.uk

Blocks, transactions, addresses, network hashrate and difficulty, synced from our own v1.1.0 node. It runs eIquidus (open source) and is free to use, with no sign-up.

Mining is paused for a few days, so the latest block is ~53,947 for now. It updates every minute once blocks resume.

Reminder: merge-mining (AuxPoW) starts at block 56,500. Older v1.0.x nodes will stop following the chain there, so please upgrade to v1.1.0:
https://github.com/Shears-Mining/voidcoin/releases/tag/v1.1.0

If you run a node, post your IP:port here and I'll add it to the README as a seed node.

[nestex_one]

VoidCoin revived – source preserved, v1.1.0 merge-mining (auxpow) with Bitcoin from block 56,500[/b]

We had listed $VOID, but it'd been de-listed when the dev left. We have a full record of all past balances, old wallets and multiple snapshots of our old working node.

Can you confirm if the old balances are preserved and if our users should treat it as a 'recovery' or a 'new chain'.

[solarsurfer]

VoidCoin revived – source preserved, v1.1.0 merge-mining (auxpow) with Bitcoin from block 56,500[/b]

We had listed $VOID, but it'd been de-listed when the dev left. We have a full record of all past balances, old wallets and multiple snapshots of our old working node.

Can you confirm if the old balances are preserved and if our users should treat it as a 'recovery' or a 'new chain'.

Thanks for getting in touch, and good to hear you kept records.

Short answer: it's a recovery, the same chain. Nothing was restarted, re-launched or snapshotted. Our nodes run the original VoidHash-Crypto code (v1.0.5, unchanged), synced the original chain from the genesis block, and we have simply kept mining on top of it. All past balances on that chain are preserved exactly as they were, and old wallets work as before. Personally, I don't think there is any other way that makes all this hard work worthwhile !

How you can confirm it yourselves

• Look up any of your old addresses on the explorer: https://void-explorer.shears.co.uk. Balances and full history should match your records.
• Compare a block hash: take the latest block height in one of your node snapshots, run voidcoin-cli getblockhash <height> on it, and check it against the same height on the explorer. If the hashes match, your snapshot and our chain are the same chain up to that point. If they differ, please post the height and both hashes and we'll look into it together.

Important for your users and your node
Merge-mining (AuxPoW) activates at block 56,500. Older v1.0.x nodes will stop following the chain at that height, so any node or wallet you run needs upgrading to v1.1.0 before then (Linux and Windows builds, source preserved with the original history):
https://github.com/Shears-Mining/voidcoin/releases/tag/v1.1.0

Old wallet files are fully compatible: back them up, install v1.1.0, and the balances appear once the node has synced. (Nobody needs to send their wallet to anyone, ever.)

If you'd like to relist, I'm happy to help with node setup or anything you need, and I can add your node to the seed list in the README.

[nestex_one]

VoidCoin revived – source preserved, v1.1.0 merge-mining (auxpow) with Bitcoin from block 56,500[/b]

We had listed $VOID, but it'd been de-listed when the dev left. We have a full record of all past balances, old wallets and multiple snapshots of our old working node.

Can you confirm if the old balances are preserved and if our users should treat it as a 'recovery' or a 'new chain'.

Thanks for getting in touch, and good to hear you kept records.

Short answer: it's a recovery, the same chain. Nothing was restarted, re-launched or snapshotted. Our nodes run the original VoidHash-Crypto code (v1.0.5, unchanged), synced the original chain from the genesis block, and we have simply kept mining on top of it. All past balances on that chain are preserved exactly as they were, and old wallets work as before. Personally, I don't think there is any other way that makes all this hard work worthwhile !

How you can confirm it yourselves

• Look up any of your old addresses on the explorer: https://void-explorer.shears.co.uk. Balances and full history should match your records.
• Compare a block hash: take the latest block height in one of your node snapshots, run voidcoin-cli getblockhash <height> on it, and check it against the same height on the explorer. If the hashes match, your snapshot and our chain are the same chain up to that point. If they differ, please post the height and both hashes and we'll look into it together.

Important for your users and your node
Merge-mining (AuxPoW) activates at block 56,500. Older v1.0.x nodes will stop following the chain at that height, so any node or wallet you run needs upgrading to v1.1.0 before then (Linux and Windows builds, source preserved with the original history):
https://github.com/Shears-Mining/voidcoin/releases/tag/v1.1.0

Old wallet files are fully compatible: back them up, install v1.1.0, and the balances appear once the node has synced. (Nobody needs to send their wallet to anyone, ever.)

If you'd like to relist, I'm happy to help with node setup or anything you need, and I can add your node to the seed list in the README.

Just one thing: I would recommend talking to the original dev and get an OK from him before you put in a lot of effort on this. I know it's open source but there can be ethical issues when it comes to running a chain if the previous dev is still active (as we're aware he is in the community).

We get the message "wallet requires newer version of voidcoin core"

Code:

2026-10-25T22:00:46Z Verification: No coin database inconsistencies in last 6 blocks (6 transactions)
2026-10-25T22:00:46Z Block index and chainstate loaded
2026-10-25T22:00:46Z Using SQLite Version 3.46.1
2026-10-25T22:00:46Z init message: Loading wallet…
2026-10-25T22:00:46Z [wallet] Wallet file version = 10500, last client version = 20003
2026-10-25T22:00:46Z [wallet] Releasing wallet wallet..
2026-10-25T22:00:46Z [error] Error loading wallet.dat: Wallet requires newer version of VoidCoin Core
2026-10-25T22:01:30Z Shutdown: In progress...
2026-10-25T22:01:30Z scheduler thread exit
2026-10-25T22:01:30Z Flushed fee estimates to fee_estimates.dat.
2026-10-25T22:01:30Z Shutdown: done

[solarsurfer]

VoidCoin revived – source preserved, v1.1.0 merge-mining (auxpow) with Bitcoin from block 56,500[/b]

We had listed $VOID, but it'd been de-listed when the dev left. We have a full record of all past balances, old wallets and multiple snapshots of our old working node.

Can you confirm if the old balances are preserved and if our users should treat it as a 'recovery' or a 'new chain'.

Thanks for getting in touch, and good to hear you kept records.

Short answer: it's a recovery, the same chain. Nothing was restarted, re-launched or snapshotted. Our nodes run the original VoidHash-Crypto code (v1.0.5, unchanged), synced the original chain from the genesis block, and we have simply kept mining on top of it. All past balances on that chain are preserved exactly as they were, and old wallets work as before. Personally, I don't think there is any other way that makes all this hard work worthwhile !

How you can confirm it yourselves

• Look up any of your old addresses on the explorer: https://void-explorer.shears.co.uk. Balances and full history should match your records.
• Compare a block hash: take the latest block height in one of your node snapshots, run voidcoin-cli getblockhash <height> on it, and check it against the same height on the explorer. If the hashes match, your snapshot and our chain are the same chain up to that point. If they differ, please post the height and both hashes and we'll look into it together.

Important for your users and your node
Merge-mining (AuxPoW) activates at block 56,500. Older v1.0.x nodes will stop following the chain at that height, so any node or wallet you run needs upgrading to v1.1.0 before then (Linux and Windows builds, source preserved with the original history):
https://github.com/Shears-Mining/voidcoin/releases/tag/v1.1.0

Old wallet files are fully compatible: back them up, install v1.1.0, and the balances appear once the node has synced. (Nobody needs to send their wallet to anyone, ever.)

If you'd like to relist, I'm happy to help with node setup or anything you need, and I can add your node to the seed list in the README.

Just one thing: I would recommend talking to the original dev and get an OK from him before you put in a lot of effort on this. I know it's open source but there can be ethical issues when it comes to running a chain if the previous dev is still active (as we're aware he is in the community).

We get the message "wallet requires newer version of voidcoin core"

Code:

2026-10-25T22:00:46Z Verification: No coin database inconsistencies in last 6 blocks (6 transactions)
2026-10-25T22:00:46Z Block index and chainstate loaded
2026-10-25T22:00:46Z Using SQLite Version 3.46.1
2026-10-25T22:00:46Z init message: Loading wallet…
2026-10-25T22:00:46Z [wallet] Wallet file version = 10500, last client version = 20003
2026-10-25T22:00:46Z [wallet] Releasing wallet wallet..
2026-10-25T22:00:46Z [error] Error loading wallet.dat: Wallet requires newer version of VoidCoin Core
2026-10-25T22:01:30Z Shutdown: In progress...
2026-10-25T22:01:30Z scheduler thread exit
2026-10-25T22:01:30Z Flushed fee estimates to fee_estimates.dat.
2026-10-25T22:01:30Z Shutdown: done

Hi, Thanks, both points are really helpful.

On the original dev: you're right, and I'd much rather do this with his blessing. But before I started, the GitHub repo was gone and emails to the team bounced, plus every other way of contact failed, their launch data, website, explorer, Discord also failed, so I assumed (How much extra data do I need in order to say to myself, eh up, they have done a runner!) nobody was left - that's the only reason I picked it up. If he's still active, could you tell me the best way to reach him? I'm happy to work with him, hand things over, or step back, whatever he prefers. Until we've spoken I'll keep merge-mining on hold: it only activates at block 56,500, and I've paused mining well below that, so nothing changes on the chain in the meantime. If nobody appears, then Ill continue.

On the wallet error: your log says the wallet was last opened by VoidCoin Core 2.0.3 ("last client version = 20003"). That's a version I've never seen - the public releases I preserved stopped at v1.0.5 - so an older client refusing a wallet written by 2.0.3 is expected. Please keep that wallet.dat backed up and don't try to "repair" it.

Could you tell me:
- where you got 2.0.3 (download link or the dev), and whether you still have it ?
- and, from a node running it: voidcoin-cli getblockhash 50000 ?
so we can check that 2.0.3 is on the same chain as everyone else.

If 2.0.3 runs on the same chain, simply keep using it to open that wallet - your coins are on the chain, not in the software.

Also, on their official launch page (only remining data, due to them closing down their website) mentions nothing about any new release above V1.02, but I do know v 1.05 did appear. There is no way a coin would jump from that version, to V2.03, there would also be a faint trail if V2 ever appeared.

What I think is more likely. Is that because there is passed "History" shall we say with code from Kvanta5, its more than likely, that at some stage you inherited a mystery wallet of (Voidcoin) Kvanta 5 version. If someone opened that wallet with Kvanta5 software at some point, that would explain it.

Regards

[BitcoinII-Dev]

VoidCoin revived – source preserved, v1.1.0 merge-mining (auxpow) with Bitcoin from block 56,500[/b]

We had listed $VOID, but it'd been de-listed when the dev left. We have a full record of all past balances, old wallets and multiple snapshots of our old working node.

Can you confirm if the old balances are preserved and if our users should treat it as a 'recovery' or a 'new chain'.

Thanks for getting in touch, and good to hear you kept records.

Short answer: it's a recovery, the same chain. Nothing was restarted, re-launched or snapshotted. Our nodes run the original VoidHash-Crypto code (v1.0.5, unchanged), synced the original chain from the genesis block, and we have simply kept mining on top of it. All past balances on that chain are preserved exactly as they were, and old wallets work as before. Personally, I don't think there is any other way that makes all this hard work worthwhile !

How you can confirm it yourselves

• Look up any of your old addresses on the explorer: https://void-explorer.shears.co.uk. Balances and full history should match your records.
• Compare a block hash: take the latest block height in one of your node snapshots, run voidcoin-cli getblockhash <height> on it, and check it against the same height on the explorer. If the hashes match, your snapshot and our chain are the same chain up to that point. If they differ, please post the height and both hashes and we'll look into it together.

Important for your users and your node
Merge-mining (AuxPoW) activates at block 56,500. Older v1.0.x nodes will stop following the chain at that height, so any node or wallet you run needs upgrading to v1.1.0 before then (Linux and Windows builds, source preserved with the original history):
https://github.com/Shears-Mining/voidcoin/releases/tag/v1.1.0

Old wallet files are fully compatible: back them up, install v1.1.0, and the balances appear once the node has synced. (Nobody needs to send their wallet to anyone, ever.)

If you'd like to relist, I'm happy to help with node setup or anything you need, and I can add your node to the seed list in the README.

Just one thing: I would recommend talking to the original dev and get an OK from him before you put in a lot of effort on this. I know it's open source but there can be ethical issues when it comes to running a chain if the previous dev is still active (as we're aware he is in the community).

We get the message "wallet requires newer version of voidcoin core"

Code:

2026-10-25T22:00:46Z Verification: No coin database inconsistencies in last 6 blocks (6 transactions)
2026-10-25T22:00:46Z Block index and chainstate loaded
2026-10-25T22:00:46Z Using SQLite Version 3.46.1
2026-10-25T22:00:46Z init message: Loading wallet…
2026-10-25T22:00:46Z [wallet] Wallet file version = 10500, last client version = 20003
2026-10-25T22:00:46Z [wallet] Releasing wallet wallet..
2026-10-25T22:00:46Z [error] Error loading wallet.dat: Wallet requires newer version of VoidCoin Core
2026-10-25T22:01:30Z Shutdown: In progress...
2026-10-25T22:01:30Z scheduler thread exit
2026-10-25T22:01:30Z Flushed fee estimates to fee_estimates.dat.
2026-10-25T22:01:30Z Shutdown: done

Hi, Thanks, both points are really helpful.

On the original dev: you're right, and I'd much rather do this with his blessing. But before I started, the GitHub repo was gone and emails to the team bounced, plus every other way of contact failed, their launch data, website, explorer, Discord also failed, so I assumed (How much extra data do I need in order to say to myself, eh up, they have done a runner!) nobody was left - that's the only reason I picked it up. If he's still active, could you tell me the best way to reach him? I'm happy to work with him, hand things over, or step back, whatever he prefers. Until we've spoken I'll keep merge-mining on hold: it only activates at block 56,500, and I've paused mining well below that, so nothing changes on the chain in the meantime. If nobody appears, then Ill continue.

On the wallet error: your log says the wallet was last opened by VoidCoin Core 2.0.3 ("last client version = 20003"). That's a version I've never seen - the public releases I preserved stopped at v1.0.5 - so an older client refusing a wallet written by 2.0.3 is expected. Please keep that wallet.dat backed up and don't try to "repair" it.

Could you tell me:
- where you got 2.0.3 (download link or the dev), and whether you still have it ?
- and, from a node running it: voidcoin-cli getblockhash 50000 ?
so we can check that 2.0.3 is on the same chain as everyone else.

If 2.0.3 runs on the same chain, simply keep using it to open that wallet - your coins are on the chain, not in the software.

Also, on their official launch page (only remining data, due to them closing down their website) mentions nothing about any new release above V1.02, but I do know v 1.05 did appear. There is no way a coin would jump from that version, to V2.03, there would also be a faint trail if V2 ever appeared.

What I think is more likely. Is that because there is passed "History" shall we say with code from Kvanta5, its more than likely, that at some stage you inherited a mystery wallet of (Voidcoin) Kvanta 5 version. If someone opened that wallet with Kvanta5 software at some point, that would explain it.

Regards

Liam released something like 4–8 "updates" in a single 24-hour period while experimenting with his idea of "Quantum Uncertain Difficulty."

Interestingly, several of those "updates" ended up having different SHA-256 hashes for the same platform binaries and source tarballs/zips, despite carrying identical version numbers.
Which binary/source tarball/zip you actually received apparently depended on what time of day you happened to visit the GitHub repository.
The "Quantum Uncertainty" is now certain: It's certain that nobody holding any surviving piece of the blockchain he abandoned is going to have the slightest
idea where to begin putting everything back together, determining which software version they're actually running, or getting their nodes back onto the correct chain tip.
He set out to make the mining difficulty quantum-uncertain and somehow managed to make the entire software distribution and blockchain recovery process uncertain instead.

As for NestEx's suggestion to check with Liam before proceeding... Don't bother. He doesn't give a shit. He's already moved on to the next shiny thing, and the next shiny thing after that.
Now it's Frio-something-or-other and XBTCash. As far Liam is concerned, Void was dead to him the moment he pulled its trading liquidity from NestEx. I see absolutely no reason why someone
willing to put in the time and effort to recover an abandoned blockchain should have to seek the blessing of the person who abandoned it in the first place.
If he wanted to retain stewardship of the project, he had every opportunity to do so. Instead, somebody else is now doing the work required to keep it alive.

As far as the Kvanta5 team is concerned, we don't care what you do with the code as long as the proper copyrights are preserved and properly attributed.

Good luck with the recovery. You've certainly got your work cut out for you.

[BitcoinII-Dev]

Also, this:

"What I think is more likely. Is that because there is passed "History" shall we say with code from Kvanta5, its more than likely, that at some stage you inherited a mystery wallet of (Voidcoin) Kvanta 5 version.
If someone opened that wallet with Kvanta5 software at some point, that would explain it. "


Two things:

NestEx isn't that dumb.

And if your reasoning for suspecting NestEx's wallet warning is to automatically jump to the conclusion of "Oh, they must've opened it with KV5's software! That's gotta be it!", then
you probably shouldn't try to resurrect this thing by yourself. See if you can find some experienced help. It'll save you a lot of lessons being learned "the hard way" unnecessarily.

[solarsurfer]

Also, this:

"What I think is more likely. Is that because there is passed "History" shall we say with code from Kvanta5, its more than likely, that at some stage you inherited a mystery wallet of (Voidcoin) Kvanta 5 version.
If someone opened that wallet with Kvanta5 software at some point, that would explain it. "


Two things:

NestEx isn't that dumb.

And if your reasoning for suspecting NestEx's wallet warning is to automatically jump to the conclusion of "Oh, they must've opened it with KV5's software! That's gotta be it!", then
you probably shouldn't try to resurrect this thing by yourself. See if you can find some experienced help. It'll save you a lot of lessons being learned "the hard way" unnecessarily.

Fair point - the KV5 idea was only a guess on my part, and I shouldn't have floated it. The far likelier answer is that NestEx was given a 2.0.3 build by the original team that was never published, which is exactly why I've asked them about it.

To be clear about where things stand: the chain itself hasn't been touched. It's the original v1.0.5 code and chain, with full history, and anyone can verify that against the explorer and the preserved source. Merge-mining is on hold until I've heard from NestEx and, hopefully, the original dev.

If you have experience with this codebase, help and review are genuinely welcome - the source is all public.

Best Regards

[BitcoinII-Dev]

Also, this:

"What I think is more likely. Is that because there is passed "History" shall we say with code from Kvanta5, its more than likely, that at some stage you inherited a mystery wallet of (Voidcoin) Kvanta 5 version.
If someone opened that wallet with Kvanta5 software at some point, that would explain it. "


Two things:

NestEx isn't that dumb.

And if your reasoning for suspecting NestEx's wallet warning is to automatically jump to the conclusion of "Oh, they must've opened it with KV5's software! That's gotta be it!", then
you probably shouldn't try to resurrect this thing by yourself. See if you can find some experienced help. It'll save you a lot of lessons being learned "the hard way" unnecessarily.

Fair point - the KV5 idea was only a guess on my part, and I shouldn't have floated it. The far likelier answer is that NestEx was given a 2.0.3 build by the original team that was never published, which is exactly why I've asked them about it.

To be clear about where things stand: the chain itself hasn't been touched. It's the original v1.0.5 code and chain, with full history, and anyone can verify that against the explorer and the preserved source. Merge-mining is on hold until I've heard from NestEx and, hopefully, the original dev.

If you have experience with this codebase, help and review are genuinely welcome - the source is all public.

Best Regards

Void 2.0.3 was definitely published. It had to be, as "QUD" from the 1.0.+ versions was a disaster. NestEx is something in the neighborhood of 3+ hard forks
of the chain from a consensus standpoint than you are. Their view of the chain is canonical, your view of the chain is not.

I can't enumerate all of the exact changes of the codebase from what you have to what NestEx has, as there were many and I simply don't care to try to remember them all.

What I can tell you is that if you want to revive this thing properly, you need the codebase that NestEx has. That preserves the full length of canonical chain, and none of the
original miners or traders will have lost any coins. You will be the one losing coins by abandoning the current chain fork you have created in your revival attempt.

I don't have a copy of 2.0.3, or I'd give it to you.

[solarsurfer]

Also, this:

"What I think is more likely. Is that because there is passed "History" shall we say with code from Kvanta5, its more than likely, that at some stage you inherited a mystery wallet of (Voidcoin) Kvanta 5 version.
If someone opened that wallet with Kvanta5 software at some point, that would explain it. "


Two things:

NestEx isn't that dumb.

And if your reasoning for suspecting NestEx's wallet warning is to automatically jump to the conclusion of "Oh, they must've opened it with KV5's software! That's gotta be it!", then
you probably shouldn't try to resurrect this thing by yourself. See if you can find some experienced help. It'll save you a lot of lessons being learned "the hard way" unnecessarily.

Fair point - the KV5 idea was only a guess on my part, and I shouldn't have floated it. The far likelier answer is that NestEx was given a 2.0.3 build by the original team that was never published, which is exactly why I've asked them about it.

To be clear about where things stand: the chain itself hasn't been touched. It's the original v1.0.5 code and chain, with full history, and anyone can verify that against the explorer and the preserved source. Merge-mining is on hold until I've heard from NestEx and, hopefully, the original dev.

If you have experience with this codebase, help and review are genuinely welcome - the source is all public.

Best Regards

Void 2.0.3 was definitely published. It had to be, as "QUD" from the 1.0.+ versions was a disaster. NestEx is something in the neighborhood of 3+ hard forks
of the chain from a consensus standpoint than you are. Their view of the chain is canonical, your view of the chain is not.

I can't enumerate all of the exact changes of the codebase from what you have to what NestEx has, as there were many and I simply don't care to try to remember them all.

What I can tell you is that if you want to revive this thing properly, you need the codebase that NestEx has. That preserves the full length of canonical chain, and none of the
original miners or traders will have lost any coins. You will be the one losing coins by abandoning the current chain fork you have created in your revival attempt.

I don't have a copy of 2.0.3, or I'd give it to you.

Thanks again for your patience. I've checked our chain history, and here is exactly where things stand.

Our node saw the original network mine steadily up to block 49,390 (7 Aug 2026), then nothing for 60 days, until I restarted mining on 7 Oct. If 2.0.x was a hard fork around then, our v1.0.5 node would have stopped following at that point, so it's possible your chain continued without us.

Could you run these on your node and send me the results?

  voidcoin-cli getblockcount
  voidcoin-cli getblockhash 49390
  voidcoin-cli getblockhash 49391

Ours are:
  49390: 000000000000105fb377c3ce7c919d406a4a2530fd4abb08cd00e2352f8627d1
  49391: 0000000000000a0e563e303cd29764fbf998e3ebd4f9fe479253be2d31833887

If your chain went on past 49,390 with different blocks, yours is the canonical chain and I'll move to it. I'd only ask for a copy of 2.0.3 (or where to get it) so it can be preserved and built on properly. No original holder would lose anything either way: every balance up to block 49,390 is identical on both.

Thanks,
Andy

[BitcoinII-Dev]

Also, this:

"What I think is more likely. Is that because there is passed "History" shall we say with code from Kvanta5, its more than likely, that at some stage you inherited a mystery wallet of (Voidcoin) Kvanta 5 version.
If someone opened that wallet with Kvanta5 software at some point, that would explain it. "


Two things:

NestEx isn't that dumb.

And if your reasoning for suspecting NestEx's wallet warning is to automatically jump to the conclusion of "Oh, they must've opened it with KV5's software! That's gotta be it!", then
you probably shouldn't try to resurrect this thing by yourself. See if you can find some experienced help. It'll save you a lot of lessons being learned "the hard way" unnecessarily.

Fair point - the KV5 idea was only a guess on my part, and I shouldn't have floated it. The far likelier answer is that NestEx was given a 2.0.3 build by the original team that was never published, which is exactly why I've asked them about it.

To be clear about where things stand: the chain itself hasn't been touched. It's the original v1.0.5 code and chain, with full history, and anyone can verify that against the explorer and the preserved source. Merge-mining is on hold until I've heard from NestEx and, hopefully, the original dev.

If you have experience with this codebase, help and review are genuinely welcome - the source is all public.

Best Regards

Void 2.0.3 was definitely published. It had to be, as "QUD" from the 1.0.+ versions was a disaster. NestEx is something in the neighborhood of 3+ hard forks
of the chain from a consensus standpoint than you are. Their view of the chain is canonical, your view of the chain is not.

I can't enumerate all of the exact changes of the codebase from what you have to what NestEx has, as there were many and I simply don't care to try to remember them all.

What I can tell you is that if you want to revive this thing properly, you need the codebase that NestEx has. That preserves the full length of canonical chain, and none of the
original miners or traders will have lost any coins. You will be the one losing coins by abandoning the current chain fork you have created in your revival attempt.

I don't have a copy of 2.0.3, or I'd give it to you.

Thanks again for your patience. I've checked our chain history, and here is exactly where things stand.

Our node saw the original network mine steadily up to block 49,390 (7 Aug 2026), then nothing for 60 days, until I restarted mining on 7 Oct. If 2.0.x was a hard fork around then, our v1.0.5 node would have stopped following at that point, so it's possible your chain continued without us.

Could you run these on your node and send me the results?

  voidcoin-cli getblockcount
  voidcoin-cli getblockhash 49390
  voidcoin-cli getblockhash 49391

Ours are:
  49390: 000000000000105fb377c3ce7c919d406a4a2530fd4abb08cd00e2352f8627d1
  49391: 0000000000000a0e563e303cd29764fbf998e3ebd4f9fe479253be2d31833887

If your chain went on past 49,390 with different blocks, yours is the canonical chain and I'll move to it. I'd only ask for a copy of 2.0.3 (or where to get it) so it can be preserved and built on properly. No original holder would lose anything either way: every balance up to block 49,390 is identical on both.

Thanks,
Andy

Andy,

      I can appreciate what you're trying to do, so I'm going to help you out the only way I can think of at the moment. I called a friend, and called in a favor.
Luckily for you, he had a copy of v2.0.3 he was happy to send me. I fixed the copyright issues that got the original Void repository taken down due to DMCA violations,
and put it up on GitHub so you can clone it and get squared away and off to a more well prepared start. I'm also extending to you a One Time Use license for the code
necessary for users to retrieve their coins from any Vaults should they have any in them. When you release v2.0.4, you'll need to either: Remove the code the One Time Use
license applies to (The Vault pages, specifically), or heavily modify them from where they are now. That's the legal approach. The professional approach is to just ask for
permission to use them.

You can find v2.0.3 here: https://github.com/KvantaMechanic/VoidCoin

                                                                                                                                                                                                                                              Good Luck,
                                                                                                                                                                                                                                                    BC2-Dev, AKA KvantaMechanic

[solarsurfer]

Also, this:

"What I think is more likely. Is that because there is passed "History" shall we say with code from Kvanta5, its more than likely, that at some stage you inherited a mystery wallet of (Voidcoin) Kvanta 5 version.
If someone opened that wallet with Kvanta5 software at some point, that would explain it. "


Two things:

NestEx isn't that dumb.

And if your reasoning for suspecting NestEx's wallet warning is to automatically jump to the conclusion of "Oh, they must've opened it with KV5's software! That's gotta be it!", then
you probably shouldn't try to resurrect this thing by yourself. See if you can find some experienced help. It'll save you a lot of lessons being learned "the hard way" unnecessarily.

Fair point - the KV5 idea was only a guess on my part, and I shouldn't have floated it. The far likelier answer is that NestEx was given a 2.0.3 build by the original team that was never published, which is exactly why I've asked them about it.

To be clear about where things stand: the chain itself hasn't been touched. It's the original v1.0.5 code and chain, with full history, and anyone can verify that against the explorer and the preserved source. Merge-mining is on hold until I've heard from NestEx and, hopefully, the original dev.

If you have experience with this codebase, help and review are genuinely welcome - the source is all public.

Best Regards

Void 2.0.3 was definitely published. It had to be, as "QUD" from the 1.0.+ versions was a disaster. NestEx is something in the neighborhood of 3+ hard forks
of the chain from a consensus standpoint than you are. Their view of the chain is canonical, your view of the chain is not.

I can't enumerate all of the exact changes of the codebase from what you have to what NestEx has, as there were many and I simply don't care to try to remember them all.

What I can tell you is that if you want to revive this thing properly, you need the codebase that NestEx has. That preserves the full length of canonical chain, and none of the
original miners or traders will have lost any coins. You will be the one losing coins by abandoning the current chain fork you have created in your revival attempt.

I don't have a copy of 2.0.3, or I'd give it to you.

Thanks again for your patience. I've checked our chain history, and here is exactly where things stand.

Our node saw the original network mine steadily up to block 49,390 (7 Aug 2026), then nothing for 60 days, until I restarted mining on 7 Oct. If 2.0.x was a hard fork around then, our v1.0.5 node would have stopped following at that point, so it's possible your chain continued without us.

Could you run these on your node and send me the results?

  voidcoin-cli getblockcount
  voidcoin-cli getblockhash 49390
  voidcoin-cli getblockhash 49391

Ours are:
  49390: 000000000000105fb377c3ce7c919d406a4a2530fd4abb08cd00e2352f8627d1
  49391: 0000000000000a0e563e303cd29764fbf998e3ebd4f9fe479253be2d31833887

If your chain went on past 49,390 with different blocks, yours is the canonical chain and I'll move to it. I'd only ask for a copy of 2.0.3 (or where to get it) so it can be preserved and built on properly. No original holder would lose anything either way: every balance up to block 49,390 is identical on both.

Thanks,
Andy

Andy,

      I can appreciate what you're trying to do, so I'm going to help you out the only way I can think of at the moment. I called a friend, and called in a favor.
Luckily for you, he had a copy of v2.0.3 he was happy to send me. I fixed the copyright issues that got the original Void repository taken down due to DMCA violations,
and put it up on GitHub so you can clone it and get squared away and off to a more well prepared start. I'm also extending to you a One Time Use license for the code
necessary for users to retrieve their coins from any Vaults should they have any in them. When you release v2.0.4, you'll need to either: Remove the code the One Time Use
license applies to (The Vault pages, specifically), or heavily modify them from where they are now. That's the legal approach. The professional approach is to just ask for
permission to use them.

You can find v2.0.3 here: https://github.com/KvantaMechanic/VoidCoin

                                                                                                                                                                                                                                              Good Luck,
                                                                                                                                                                                                                                                    BC2-Dev, AKA KvantaMechanic

Thank you - genuinely. That's a real help, and I appreciate you calling in a favour to get it.

I've forked it to preserve it, and checked it against the original Windows build of 2.0.3 that NestEx's team kindly sent me: same version, same VCIP-3 rules and settings. NestEx's 2.0.3 node also ends at block 49,390 with the identical hash to our chain, so everything lines up. VCIP-3 activated at 32,000, well before that. I'll test 2.0.3 against the blocks since then before going further.

On the Vault pages: consider this me asking properly. May I have your permission to keep them in future VoidCoin releases (with full Kvanta5 credit), so holders can always reach their vault coins? If you'd rather not, I'll remove them as you describe.

And credit where it's due - the README now says at the top that VoidCoin is built on Kvanta5-Core and that the quantum-resistant work is your team's.

Thanks again,
Andy