00:24:13 * monerod is storing the cumulative difficulty as a uint_128t (theoricaly as its boost), but for now the cumulative difficulty (269952836198516580) have reached 1.46% of the total value a uint_64t can take. Is there any chance in a reasonable future that the upper 64 bits can be occupied? 00:30:32 someoneelse49549: https://github.com/monero-project/monero/pull/5239 19:18:40 I'm trying to use monero mining as a form of user authentication/micropayment. The current approach is to use the monerod rpc api and XMrig as a basic mining pool. I need to test if my job validator is working and if my app submits valid shares/blocks. Since it takes too long to verify this on mainnet I'm currently syncing Stagenet to see if the 19:18:40 difficulty is low enough to confirm any of my shares. Is this the right way of going about the task, or how would I test my miner/app with lower target difficulty? 19:21:38 You can run with --offline --fixed-difficulty N. I do that. Very useful. 19:22:47 Also, if you've not already seen it: https://repo.getmonero.org/selene/primo 19:24:24 Awesome thank you @moneromoo! 19:25:30 yes, that project does look quite similar to what I'm doing. :D 21:12:45 You might want to submit shares to p2pool-mini instead of the daemon, for better payout consistency 21:34:13 Hi merope1. I did consider that but I think it doesn't quite fit my use case. My app communicates on i2p only. As far as I understand p2pool can't do that quite yet. That's why I'm trying the long route of creating the own pool.