Where is the proof the code is 3 years old?
this is technical, get someone who actually understand programming to verify it for you if you dont believe me.
it is well known that dgb forked from myriad, if you go to the myriad github repo
https://github.com/myriadcoin/myriadcoin you will see some info at top left, 1) myriad itself has only done 151 commits 2) myriad forked from zetacoin
we then go to zetacoins github
https://github.com/zetacoin/zetacoin you will see some info at top left 1) zetacoin forked from bitcoin 2) it is an amazing 6103 commits behind bitcoin
from this we can infer that myriad was also 6103 commits behind bitcoin, and that when digibyte was forked from myriad it would also then be 6103 commits behind.
of course at this point you are going to claim digibyte updated the code after forking, but here is a simple script that will prove you wrong
rm -rf dgb
rm -rf myr
#clone the 2 for comparison
git clone https://github.com/digibyte/digibyte.git
git clone https://github.com/myriadcoin/myriadcoin.git
cp -rf myriadcoin myr
cp -rf digibyte dgb
#normalise name changes for comparison
find myr -type f -exec sed -i 's/bitcoin/shitcoin/gI' {} +
find myr -type f -exec sed -i 's/digibyte/shitcoin/gI' {} +
find myr -type f -exec sed -i 's/myriadcoin/shitcoin/gI' {} +
find myr -type f -exec sed -i 's/myriad/shitcoin/gI' {} +
find dgb -type f -exec sed -i 's/bitcoin/shitcoin/gI' {} +
find dgb -type f -exec sed -i 's/digibyte/shitcoin/gI' {} +
find dgb -type f -exec sed -i 's/myriadcoin/shitcoin/gI' {} +
find dgb -type f -exec sed -i 's/myriad/shitcoin/gI' {} +
#delete images and localisation files as these are not code and create a lot of noise
rm -rf dgb/src/qt/res
rm -rf myr/src/qt/res
rm -rf dgb/src/qt/locale
rm -rf myr/src/qt/locale
#compare the src directories to get an idea of how much code has been added
diff -rubd myr/src/ dgb/src/ | grep -E "^[+][^+]" | wc -l
if you run this script you will find that there are only (and this is an upper bound) 1118 differences (most of these are from myriad side, as I showed in my earlier posts the entire code written by th e digibyte team is as little as 500 lines with most of that being generic stuff a child could change) between the current myriad and digibyte codebases if digibyte had updates to the latest bitcoin these differences would be much greater.
from this it is safe to infer that digibyte is on the same bitcoin codebase as zetacoin and myriad - the exact bitcoin commit zetacoin forked from is here
https://github.com/bitcoin/bitcoin/commit/6d89611c3aaa85798c4d70d20e35e6bcb7bdd5c0 and dates back to 2013 meaning digibyte is terribly out of date and missing lots of features and bug fixes from bitcoin
of course I expect you still wont believe me so here is another script
rm -rf dgb
rm -rf btc
rm -rf btcforkpoint
#clone the 2 for comparison
git clone https://github.com/digibyte/digibyte.git
git clone https://github.com/bitcoin/bitcoin.git
cp -rf digibyte dgb
cp -rf bitcoin btc
cp -rd bitcoin btcforkpoint
#revert the repo to the point where digibyte was forked from
cd btcforkpoint
git reset --hard 6d89611c3aaa85798c4d70d20e35e6bcb7bdd5c0
cd ..
#normalise name changes for comparison
find dgb -type f -exec sed -i 's/bitcoin/shitcoin/gI' {} +
find dgb -type f -exec sed -i 's/digibyte/shitcoin/gI' {} +
find btc -type f -exec sed -i 's/bitcoin/shitcoin/gI' {} +
find btc -type f -exec sed -i 's/digibyte/shitcoin/gI' {} +
find btcforkpoint -type f -exec sed -i 's/bitcoin/shitcoin/gI' {} +
find btcforkpoint -type f -exec sed -i 's/digibyte/shitcoin/gI' {} +
#delete images and localisation files as these are not code and create a lot of noise
rm -rf dgb/src/qt/res
rm -rf btc/src/qt/res
rm -rf btcforkpoint/src/qt/res
rm -rf dgb/src/qt/locale
rm -rf btc/src/qt/locale
rm -rf btcforkpoint/src/qt/locale
#compare the src directories to get a basic idea of how much is different
diff -rubd dgb/src/ btc/src/ | grep -E "^[+][^+]" | wc -l
diff -rubd dgb/src btcforkpoint/src/ | grep -E "^[+][^+]" | wc -l
this script compares the latest digibyte codebase to the current bitcoin codebase and to the 2013 bitcoin codebase, it finds the 2013 codebase much more similar, this proves that digibyte has not kept updates with bitcoin
Crypto_Beast you know your way around code, I know hackers get poached by government to work for them. Would you consider being a developer for digibyte to update the code? A good friend of mine has confirmed you are telling the truth in this regard.