OK, I uploaded my changes to my github repo
https://github.com/panopolis/Blakecoin/commits/master

Instead of using the util2.h as i previously mentioned, I took the time to replace "loop" with "while (true)". I did not test this on Windows/Mac, only Linux. Some of the edits to makefile/ qt.pro files may be Linux specific, I'm not sure. There is still the issue where make complains that there is no rule for leveldb, currently you have to run "chmod +x build_detect_platform" and then run make in the leveldb folder, and then copy the resulting *.a files from a sub directory to main leveldb directory. I'm not sure how to fix that so its automated, its not a huge inconvenience but might confuse other people trying to compile it. Hope this helps BD 

A little late, but happy birthday blakecoin

BlueDragon, After updating to ubuntu 18.10, I was unable to compile the gui-wallet. The first issue was related to openssl 1.1, which lead me to find a few related commits for other coins. In the peercoin commit, the affected code seemed very similar to blakecoins, so I tried using that as a basis to fix the openssl issue
https://github.com/peercoin/peercoin/pull/153/commits/5b09830e5de0f5105534e69dbf4acffb3255869b

There were other issues after that, I did eventually get it to compile and seems to be working however. It took a while and so I don't remember what all I had to do, should've taken notes   some errors were boost related (I used libboost 1.67), and there was an error something like this:

in src/qt/screensplash.cpp including src/util.h: error: expected "," or ";" in "#define loop for (;".

I gather that the correct solution is to replace all references to "loop" with "while (true)", but that seemed tedious so i made a second copy of util.h with the #define loop line removed, and changed splashscreen.cpp to #include that one instead. I know, very hacky but i was getting impatient   the final thing i remember changing was the makefile to add "-lboost_chrono" after "-lboost_thread" in the "LIBS =" section.

BTW I also used qt5 instead of qt4 and that didn't seem to cause any issues. when I have time I will upload my modifications to github, however im not really familiar with git commands so I'm not sure how to properly submit pull requests or whatever. It seems to be working ok but you should definetely look it over before merging since i just slapped it together to get it working.

I would suggest making it merge mined with monero if possible. This wound help a lot with security and adoption.

They literally copy + pasted my post from 2 years ago, wtf?

Thanks for the update BD, keep chugging along

How's progress BD? Any info on game/wallet dev recently?

I think it would have been best if the xspec community could have stayed as one, but there are legitimate arguments for both sides (xspec/wisp). It would seem the split was unavoidable, but what matters is how things go moving forward. My hope is that the xspec and wisp communities will coexist peacefully, and share whenever possible. There are already too many trolls stirring chaos in the larger cryptosphere. Let's remember that although people may disagree on technical or philosophical issues, we all seek a common goal of making cryptocurrency the revolution of our era.

This may still be the beginning of difficulty increase. If blakecoin continues to gain attention, and the Baikal asics are made to work correctly, the difficulty could be 100x by end of year. Keep mining and hold, even if it seems not worth it now it will be later.

Just an idea for those on (currently) unsupported OS, you could install windows in a virtual machine and install your wallet there. Not ideal, but for some people it may be an easier option than trying to compile from source.

OK that's cool, I think vcash also uses blake256r8 so they may be targeting that. Or if its for 14 round Blake they could design it to optionally iterate 8 rounds instead, getting a second hash algo "for free". Hope its compatible with blakecoin, even though I don't like the arms-race nature of PoW, it may bring wider adoption. As for switching blc to blake256r14, I agree that's not ideal, just got myself excited for a moment I remember when decred was about to launch, I tried convincing them to use 8 rounds instead of 14, but they were already too far along and had their reasons for sticking with r14. Oh well

Asics for blake256?! This is news to me, where is there info on this? I know decred will have asics coming out in 6 months or so, but that is 14 round blake256. Will those support changing the number of rounds and be compatible with blakecoin block headers? If not, would you consider switching BLC to blake256r14 so we can take advantage of the decred asics?

Dp-unique, I meant it would be nice if the payout threshold was configurable by the user, instead of a fixed amount for all miners. Not a big deal though, I just don't like getting a ton of tiny payouts. I think 1sumo is a good minimum, 2 is also OK. At least for now; when the net hash rate goes up to 10 megahash, then 0.5sumo payout may be more appropriate. The goal I think is to have the average miner receive about one payout per day. These are just my opinion, but seems to be how most pools handle it. Hope that helps, good luck with your pool

Forget which one(s) but I tried a pool that had no minimum, it was sending payouts of 0.05 or less! It would be nice to have option like you said, because I understand some people may have very low or very high hash rate

Here's a thought for sumokoin pool operators, increase minimum payout threshold to 1 or 2 sumo. I see some pools will payout in amounts less than 1 sumo, this causes block chain bloat. Maybe when net hashrate is much higher it will make sense for smaller payouts, but for now it is just generating a large number of small tx, which will cause large database size.

That makes sense, thanks for the detailed explanation.

Do you need funding? I'd bet if you organized some kind of fundraising, and showcased some of the game dev you've done, people would throw money at it and you could work on it full time and/or hire some people to help get it done.

LOL, ICO is for scams and silicon valley types (arguably the same thing ). Blakecoin is in the true spirit of cryptocoins, you can earn BLC by supporting the network by mining. Or you can buy on exchange. No premine, no airdrop, no ICO or any of that nonsense. Also blakecoin has possibly the most fair mining rewards, even now 4 years after launch, anyone can mine it and receive block rewards the same as before.

Edit: to be fair not all ICO/premine are scams, but those distribution models are easily abused for profit and control. No one can say they missed out unfairly with Blakecoin, price and mining difficulty have been pretty stable for a long time

Oh that looks neat, making btc code more modular would certainly help. In case you hadn't seen this, you may also want to check out bitcoin knots
https://bitcoinknots.org/

@CreativeReef17
Honestly unless you have free electricity its probably not going to be cost effective to mine blakecoin on old nvidia cards. Most people are probably using FPGA or Nvidia Pascal. But if you still want to give it a try, the miner version i ended up using is ccminer from here:
https://github.com/cbuchner1/ccminer
I compiled it from source using the Cuda Toolkit version 8.0 and get about 2.8GH/s on an nvidia 1060 and 850MH/s on an nvidia 750ti. When compiling make sure to include -arch=compute_61 or whatever compute version your gpu supports, you can find it here:
https://developer.nvidia.com/cuda-gpus
When you run ccminer dont forget the "-a blakecoin" flag. Also you may want to adjust the intensity with the "-i" flag, my cards get too hot if they run at max speed. Hope that helps.

Also, Happy Birthday to Blakecoin, maybe this will be there year it rises again?

@BlueDragon747 Any progress on wallet update or game dev?

Relax guys, neither aeon or sumo are scams. Both have + and - aspects, both are good and hold promise. We should be collaborating not fighting, this is what open source is about. For example, aeon could benefit by porting the sumo GUI wallet, and sumo could potentially implement the blockchain pruning code from aeon. No reason to flame each other.