Tag Archives: DogeCoin

DogeCoin VIII

Okay I am done with this project, it seems to have gotten way too strange. This morning on my IRC Chat I had a message waiting for me that said “So long and thanks for all the fish.”. Several things have weirded me out about this. First, my IRC server is internal to my network, I set it up for PezWitch and I to use, there is no access to it from outside our house. Second, the user name was DMO, which is the name of the program I have been working on,  it stands for “DogeCoin Mining Operation”. Third, when I traced the IP address of where the connection came from, it was 10.0.0.1, the IP is for node 0 of the DogeCoin Cluster. Finally, all of my work is gone, the program, the database, the source code, all of it. Mind you, this could simply be the work of a hacker, but I have to tell you, I feel a bit like I have just seen a ghost, really creeped out.

DogeCoin Part VII

The database I was speaking about earlier this week that has grown a bit faster than I expected, I originally set up to store various algorithms I was having the software use for various tasks. What I was trying to accomplish was to build a command and control function that is basically a massive decision making tree to determine which algorithm is most appropriate to the task that needs completing. I knew the database would grow as the mining software got better, new algorithms could be added, compiled in as necessary and used nearly on the fly. It is really a pretty good idea, I wish I could take credit for it, but it came from a white paper written by a Russian programer. So once the database file  got so big I had to offload it to a 1 TB hard drive, I decided I needed to have another look at it. Most of my own algorithms were written in C, now I see a variety utilities written in different types of scripting languages, running the gamut; PHP, Javascript, Python, awk, sed, and the previously mentioned LISP, you name it, its probably there.

DogeCoin Part VI

I am amazed at how far it has progressed without my intervention. Apparently the self optimizing code has been doing its job, everything is working nicely and has not needed any bug fixes for a couple of days. It seems to have recompiled itself at some point, which is exactly what the anthropomorphic bot code was suppose to do. The program has stopped writing log files, the program probably optimized this function out and I will probably have to go back in and re-add the code and blacklist it from removal. However, looking at the source code, I see a lot of added assembly language in here, since I am not familiar with ARM assembly language, it will be sometime before I can figure what it did.

My only concern is the amount of storage this project is taking up. A few days ago when I was adding the 4th node, I noticed, all the 4 GB SD cards I originally used for this project were full, so I replaced them all with 32 GB cards. Those cards are pretty cheap and I figured that would take a while to fill. I was wrong, so today I have attached the spare 1 TB drive I removed from PezWitch’s system several weeks ago and off loaded the sql database files onto it. When I have time later I will have a look at that database and see why it is expanding so fast.

DogeCoin Part V

This morning I mentioned an odd influx of DogeCoin on Christmas day according to the program logging. I did not have a chance to actually check my DogWallet prior to going to work. However, I checked it when I got home and found only 14 DogeCoin. I went back and looked at the logs and sure enough, it looked like I was acquiring coins at a ridiculous rate. My only explanation at this point is perhaps a decimal error in the logging function. I will look at the source code this weekend and see what’s up.

DogeCoin Part IV

I am very concerned this morning, I have a lot more DogeCoins than I thought I would have at this point, and I do mean A LOT. I think this might be a bug in the reporting, but I am not sure yet.

Beyond that, my rig has been running pretty well since I added the node and setup a dedicated network. The code seems to be doing what it is designed to do, which is mine DogeCoins. The code has become very low maintenance, the memory leak seems to be under control and CPU usage, while high is not pegged out.

I am in the process of cleaning up my code, making sure I have given credit where it is due and that I am not violating anyone’s copyrights. It is interesting that there is code in here I don’t remember adding in, for instance there is a call to a LISP based module. I don’t remember installing LISP or compiling any modules that used LISP. I have to admit, I did a couple of long nights running on nothing but coffee and code, so I suppose I should be happy I didn’t try to drive during that time.

 

DogeCoin Part III

So I have the software mostly going now. There were some very problematic bugs in the software, including a nasty memory leak, that kept me from finishing up this project and moving on. I went to a programming forum for some help, several people suggested I try some sort of anthropomorphic self model subroutines. Frankly, this sounded like a lot of bullshit, I figured they were pulling my chain, but with a bit of research, I discovered that self optimizing anthropomorphic software is actually a thing. I found a lot of useful code on the blog of a  software developer in Norway.

So after another lost night of working various blocks of code into my mining software, I have finally gotten a successful mostly warning free compile of the binary. This code is getting huge, I am not sure I have enough bandwidth for this, so I am buying another Raspberry Pi to add to the cluster. This thing also seems to take a lot of network resources communicating between the nodes, so as not to interfere with Netflix or World of Warcraft, I have purchased another router and setup a dedicated network to the DogeCoin Cluster. The two networks are linked, but all the node communication is done on the dedicated network and only connects to the Internet when necessary for the mining operation.

DogeCoin Part II

Step one of my project is completed. I got the Beowulf cluster up and running, ran some quick benchmarking tests on it and found it operates at approximately the speed three clustered Raspberry Pi’s. Not being a particularly brilliant programmer, I scoured the net for bits and pieces of code to help me do the optimizing of the mining software for a clustered environment. There is actually quit a lot of code snippets out there I found very useful. Digital currency programming is not really a popular subject among serious computer science researchers, so I did not find anything really pertaining to this, but rather oddly enough I got a lot of solid code I could integrate from a couple of AI research papers I found. It took me several hours properly integrate the new code and fix the strange little bugs, but I have successfully compiled my new mining software. There still seems to be some bugs, I am working them out and as soon as I have a reasonably functional binary, I will release it back to the community.

Once again, I am amused

Yesterday I found out about DogeCoins, and as everyone knows, I love a good parody. So in honor this awesome flipping of the finger to BitCoin I am going mine me some DogeCoin. However, I am not going to just run the mining software on my main machine until I get one, no, I am going to goto absurd lengths. I have 3 Rasperry Pi’s which I was using for various projects that I have finished or gotten bored with. So I am going to build a small Beowulf Cluster of Raspberry Pi’s to do the mining for me.

This morning I am assembling the hardware and configuring the OS for parallel cluster processing. This afternoon, I will have a look at the source code of the mining software and see if there are any modification I can make to optimize its use for a cluster environment. I figure, if I get this up and running before Christmas, I should have my first DogeCoin by summer.