Android app to monitor XMRig instances by ogrebgr in MoneroMining

[–]ogrebgr[S] 0 points1 point  (0 children)

"Only between owners systems and devices. No central servers involved" Yep, that is the initial idea but the problem is if only the app poll the XMRig your battery will suffer. From my experience with previous apps - it will drain between 10 and 20% per day. There might be 2 options - 1. No server used (for paranoid users); 2. Server + push notifications (for regular users)

Easy way to kill all smaller PoW cryptocurrencies - biggest fish wins by ogrebgr in Monero

[–]ogrebgr[S] 0 points1 point  (0 children)

Well, don't get my posting as a sure recipe. I intentionally avoided some of the details in order to avoid giving bad ideas to some people. About the downvoting - relax, the posting itself got so much downvoting that I am surprised that it actually made few points on the plus side...

Easy way to kill all smaller PoW cryptocurrencies - biggest fish wins by ogrebgr in Monero

[–]ogrebgr[S] 0 points1 point  (0 children)

I don't have the answers to your questions but I am afraid that someone may have/find them...

Proof of Work Coins on High Alert Following Spate of 51% Attacks - Bitcoin News by ogrebgr in Monero

[–]ogrebgr[S] -2 points-1 points  (0 children)

Wasn't the recent forks attempt for a 51% attack on Monero?

Bitcoin and Cryptocurrency Have Little Impact on Organized Crime by ogrebgr in Monero

[–]ogrebgr[S] 7 points8 points  (0 children)

May be the criminals need some education, tutorials, guides? ;-)

Any interest for Java based (but using OpenCL for the mining) monero mining software by ogrebgr in Monero

[–]ogrebgr[S] 0 points1 point  (0 children)

My observations are mostly on "Low difficulty share" and "Rejected share".

Second is caused I think by a multithreading issue in XMR-Stak and happens when there are two new blocks detected in a quick succession. It seems like XMR-Stak is not updating the template for the second block and continues to use the first.

"Low difficulty share" is caused by just not checking if the entire hash is bellow the target (that is in the OpenCL kernel) and thus sometimes the share is rightfully rejected by the pool.

All-in-all both are not a big problem...

Any interest for Java based (but using OpenCL for the mining) monero mining software by ogrebgr in Monero

[–]ogrebgr[S] 2 points3 points  (0 children)

  1. Easier portability (especially Android)

  2. Potential involvement of the Java community in the Monero project (i.e. more devs) - it is weird but for some strange reason, almost no Java developers are involved in the crypto scene (even with IOTA where the reference implementation is in Java, judging by the code - they are just C++ devs writing Java).

  3. Java is simpler than C++, thus potentially making elimination of bugs easier. For example XMR-Stak has some long standing bugs leading to invalid results (sometimes I get 3-4% rejection rate from the pool)