Quote from: PttnMe on August 17, 2018, 12:16:46 PM

Oh Ok, this is fine in this case. I just expected that there would be much more blocks, and new ones found regularly, so I thought that something was wrong. Lol, I just mined hundreds of blocks at the rate of 1 block each 3 second or so, difficulty 304 is so low. In contrast, I was unable to mine anything using the wallet's built-in miner. I might leave one mining thread for the testnet network, so developers and testers can experience more realistic behavior when using it. A Testnet explorer would be welcome too. Thank you again for your nodes, and your reply.

When you developing miner it will be better to have low difficulty, so checking if your algorithm is right will be faster, it is annoying to must wait hours or days just to check if block you found is correct

Quote from: PttnMe on August 17, 2018, 12:16:46 PM

If anyone is interested in, I merged the original gatra's miner (rminerd) and the latest dave-andersen's one (fastrie), so anyone can solo mine Riecoins using the optimized algorithm. Here is the rieMiner's GitHub repository.

Cool, my plans are to build riecoin community site with a lot HOWTOs and information about riecoin so if you don't mind will include your miner. Your source code looks very clean and ordered, it is good to have as much as possible different and various software for riecoin, that will attract more people to the community.

Quote from: PttnMe on August 17, 2018, 12:16:46 PM

Currently, you should be able to compile it easily on Linux and Windows. The miner works fine on my computer, and is currently mining blocks, but for some reason, its execution might fail in some computers. Moreover, only the old protocol Getwork is supported. I plan to work on it on September and later to add the GetBlockTemplate (and custom payout addresses) and Stratum (and pool mining as well) protocols support, a benchmark mode (dummy mining at constant difficulty), and fix remaining problems.

With what error execution fails ? You are using gmplib which is highly optimized for calculations, and big parts from it are in assembler. It gives big speedup but portability is lower, for example if you compile with gmplib optimized for i7 or xeon it will fail to run on P4. many modern compilers put by default optimizing flag -mtune=native which will auto detect CPU instructions set and will optimize for it, which can break portability too. Maybe to be portable one cpu miner you should use -march=pentium4 your code will run on any modern CPU , but you will lose speed.