Hi Dogedarkdev,
Being the dev of Dogecoindark, you would know that the blockchain for ANY scrypt based coin (or pretty much any cryptocurrency for that matter) does not store any IP addresses. The client itself does contain the initial dns seeder (which you need to update in your latest windows wallet by the way because its stale), however if the seeder disappears off the face of the earth, theres no incriminating evidence.
I'd also like to correct you in that in the case of a transaction or a found block; the users IP address is not transmitted. The block makes its way around the peer network. This issue was raised by people using blockchain.info when questioning whether blocks were coming from the pools they said they were (
https://bitcointalksearch.org/topic/blockchaininfo-is-innacurate-113860).
All coins will log details regarding node block updates and peers with IP addresses in debug.log; again irrelevant, regarding point above. In fact a quick look at the debug.log of DogecoinDark and you'll find IP addresses that will lead you no closer to a user.
Now - instead of talking shit on here, how about you go fix the off-by-one mining transaction bug, the difficulty retarget bug which seems to set the difficulty one block after its meant to and maybe compile a new Windows wallet containing all the changes you've made in the past year (seriously the newest wallet is 2014) on
https://github.com/doged/dogedsource.
Also whats with all the staking code left in the wallet from ppcoin? Clean that shit up because it literally makes you look like you don't know what you're doing.
barrystyle
im well aware of how the transactions are transmitted. i am also aware that the blockchain does not store ip addresses. im pretty sure i never said that, but feel free to put words in my mouth. user (client end) ip addresses ARE in fact, found in debug logs in most coins network nodes however. i have done extensive testing on this exact subject. if i set up a node on a typical coin network, i will see user ip addresses in its debug log, that connect to my node. if you think this isn't correct, you are mistaken. some of the staking code has remained in the source code, in case we ever get to a point where pow is no longer feasible. most likely we would merge mine before something like that happened. as far as retarget bugs, we dont have any, that i am aware of. also, ive made a ton of changes to the source code over the past year, and have made sure all of our pools and exchanges updated. you can FUD, but do it elsewhere, it wont be tolerated here, and it'll all get shot down anyway ;]
ps: also i was about to release a new qt wallet, as our source code has undergone many improvements, but then we decided to rebrand, dumbass.
also, your github repo sucks, my daughter could come up with something better than "cryptobucks"
https://github.com/barrystyle?tab=repositoriesnow scram with your FUD!
pps: blockchain.info posts the node that the tx relays from, not the user that sent it's ip haha