2 teams forked XDN code and started new coins - XUN and Soldo.
XUN is direct XDN clone have all the same features and already traded at exchanges.
So XDN tech still alive and evolving.
XUN is not a "direct XDN clone" man, come on...the total coin supply and mining reward are ridiculous (85,000,000,000 coins and a 150 XUN constant reward lol--part of the page says constant reward, another part says the reward increases with time actually so who knows), plus didn't the dev premine? I downloaded the XUN client then realized it had bad specs and deleted it. I'll stick with the original or a
legitimate fork of the original (do it right).
As far as the pool code goes...guys please don't waste time on things that have already been done. There is no problem compiling any of the digitalnote github source code, all compiles fine (Digitalnote daemon, node-cryptonote-util, cryptonote-universal-pool). If you are getting compiling errors make sure you're on linux (way easier). The pool code is a little tricky but just read the readme as it tells you what node-js version to use. As far as node-gyp it is finicky (and I forget my exact solution I would have to look it up) but if you're on linux you shouldn't have too many issues. The point is-- don't get all hung up thinking compiling is the problem, there is no problem with the digitalnote source code in a compiling sense.
That being said, if anyone is interested in taking a swipe at the pool code please take a look at what a community member had started here for attempting to fix the code:
https://github.com/DrCryptoToad/node-cryptonote-util and
https://github.com/DrCryptoToad/cryptonote-universal-pool-xdn It doesn't work yet but if you compare the outdated pool code to this attempted pool code fix in relation to official DigitalNote code block format changes from last year you will see what's going on and what needs to be changed. You're probably better off modifying the outdated pool code or remaking a new pool from scratch, but this github could provide you with some insight on what needs to be dealt with. IMO a pool code from scratch would probably be the best, but a patch to existing code would be easiest.
As far as the syncing issues that some people have, I am unsure what the issue is because I have never experienced them yet I have had a client and wallet ever since 2014?? I don't doubt anyone's experience but I'm just trying to understand why it happens to some and not others. I've also had to resync from the beginning a few times over the years when changing harddrive, moving things around etc...I'm currently on wallet v 1.0.12-beta on win 10 no sync problems if it helps anyone. I did not compile it myself though and its one version old technically.
Poll
