Dear all.
I have been involved in xdag since January this year and I have looked at the tech and the efforts put in by the development team.
I have also been the first to question a lot of the technology behind xdag, and as a result I have been silenced from the chat channels, banned by the 'community' and 'punished' for questioning the tech behind the transport layer used in xdag - DNET.
I will offer this disclaimer that i continue to mine xdag with significant hashpower and none of my findings pointed out in this post are based on prejudices or misconceptions. My considerations are based purely on the fact that this coin seems to be gaining huge value OTC by none more than hype, based on no solid foundation.
Although I have been involved in many cryptocurrencies dating all the way back to the conception of bitcoin in 2009, I initially worked on this coin (XDAG) with a few friends who wanted to simply, develop a pool for miners to mine xdag.
We set up a pool, however found some initial problems with the existing software. At first, it was considered that the software was the main issue and we then went on to build a second pool to alleviate our fears that the base tech of the coin was not the issue. After numerous issues on the first pool (continual disconnections and archive shares being lost) we built a second pool on a much more expensive (and expansive) server.
This second pool at least kept connection, but there was still a nagging issue that we could not quite put our fingers on. This second pool took around two weeks to build, sync and allow mining upon.
this was a concern.
So... we built a third pool, on a third server, even better spec than previous pools. This pool synced great, only connected by two other nodes... the previous two pools which were built for us - both 'whitelisted' in the centralized method of the DNET transport layer that XDAG employs.
Then i got to reading the actual DNET protocol.
oh shit.
If i were to set up a specific number of pools (nodes) on the network and have each connected via the whitelist, I could basically turn xdag into a local network - controlled by the number of nodes I have set up and thus; dictate where xdag coins could be produced and by whom.
...
some of you may have noticed a drop in many of the pools over the past couple of weeks?
my apologies.
...
Only a few pools remained online?
it was not my intent to cause harm.
...
why was that?
DNET testing.
...
Basically the dnet transport layer is designed to be used only as a local network, and has very limited capacity (this is why your cpu's idle at 100% when you mine xdag with your gpu's - although I have found this beneficial to other projects I have since been involved in.)
I set up a network of machines, linked to each other that concluded the network capabilities of xdag.
I left a few pools online, and most of xdag miners across the world have managed to switch over to to those pools in the past few days.
I've now powered down the 38 machines which were all running my 'local network' of xdag pools.
But let this be a warning... if someone who had BAD intentions came along, they could easily do the same as I have done and take complete control of the xdag network.. make a quick fork and move all of the xdag coins onto their local nodes (pools).
I've warned the community of xdag for many weeks now that this issue was a growing concern, and what has been the result?
truth hurts. let's ignore, ban, move along.... keep building our house on a foundation of sand(!?)
DNET AND THE WHITELIST OF XDAG are a growing concern, stop hyping a coin simply because it is the 'first mineable DAG'
all apologies.
yours in decentralised truth,
LeCoquin, Kyrusfables, Raskul.. et al...
i will post no more on XDAG.
Hey buddy, the issue started yesterday on Chinese pool.
Chinese moved like a horde to Europe/US pools and those pools crashed for too high load and some unlucky issue not related to dnet. (Well only the Sofar pool went down probably for dnet) (Our pool wasn't never tested for a so much big amount of miners).
And no one saw your 38 pools connected to the network...
Dnet need to be improved or changed with another overlay network but it is not good to create bad stories!
Thanks buddy, hope you can support us after your biggest enemy dnet will be killed