00:28:05 cohcho: "monero-pool can set diff higher than block difficulty" whare are you refering to in the source? 00:31:02 cohcho: "it's not ready for production" really? a) first pool to support rx b) only pool that does full rx mode (could go on) 00:31:13 Welcome contributions though! 00:31:39 function retarget that updates miner's diff 00:31:59 doesn't have fmin(target, job->block_template->difficulty) 00:32:17 I mean as plug&play solution not ready 00:32:21 I'm using now after few fixes 00:34:06 s/fmin/min 00:34:12 target != difficulty 00:34:51 wait, let me check 00:35:06 they are different things 00:37:22 "I mean as plug&play solution" <- no, there is no Dockerfile if that's what you mean. 00:40:20 "fmin(target, job->block_template->difficulty)" <- would be wrong, as I say, target is not the same thing as block difficulty. 00:41:44 you're wrong: in your code job->target equals to diff from monerod 00:42:11 functino target_to_hex produces hex of something that is called target in monerod 00:42:24 and job->target can be set higher diff in monerod 00:42:31 i'm right, check your code 00:43:28 there is no "target in monerod" 00:43:42 let me check 00:43:48 target is a stratum specific thing 00:44:46 you will find a near identical retarget in nodejs-pool 00:46:20 I didn't use nodejs-pool 00:46:30 from monerod: check_hash_64(hash, difficulty.convert_to()) 00:46:44 result of `difficulty.convert_to()` is called target 00:46:51 and difficulty itselt is difficulty 00:46:59 in your code job->target equals to difficulty 00:47:09 no no no 00:47:17 it does not. 00:47:18 and target_to_hex(job->target) equals to difficulty.convert_to but reduced to 32bits 00:47:52 If i'm wrong then i need more time to realize it 00:47:55 look at node-js updateDifficulty 00:48:28 difficulty and target (the words) get interchanged a lot in the pool(s). 00:49:16 block difficulty (at least in monero-pool, cant remember nodesjs) is the actual normal block difficulty. 00:49:47 target is something else. it still relates to difficulty, but it is not the same. 00:49:54 Write here something like: "I'm sure that monero-pool can't set miner's job complexiter higher that required for actual block" 00:49:59 And i'm will be fine 00:50:09 complexity* 00:50:31 I am absolutely positive. 00:50:54 Because of the difficulty cap more than anything else. 00:51:13 Both of the main node pool imeplementations have a ceiling I think. 00:51:28 Snipa, can you check his code? 00:51:37 You got a link? I haven't looked in forever. 00:51:55 trace retarget() function call and how it is being passed to miner via json 00:52:27 I gathered, I just don't know where trhe source code is offhand. 00:52:38 Snipa: https://github.com/jtgrassie/monero-pool/blob/master/src/pool.c#L831 which is essentially the same is https://github.com/Snipa22/nodejs-pool/blob/master/lib/pool.js#L401 00:52:48 https://github.com/jtgrassie/monero-pool/blob/master/src/pool.c#L835 00:52:50 yes, that link 00:53:24 cohcho is not grasping how startum target does not equal monero block difficulty. 00:53:36 It does, technically. 00:53:47 well yes, in reverse 00:53:49 The stratum target is the mindiff required to hit. 00:54:02 Technically, that code doesn't have a ceiling. 00:54:14 awesome! 00:54:27 neither does nodejs 00:54:31 It does: https://github.com/Snipa22/nodejs-pool/blob/master/lib/pool.js#L418 00:54:34 they don't need it 00:54:36 We lock you out during the set. :P 00:54:56 But that was more to deal with dumb miners who set massive diffs then complained about never finding shares. 00:55:16 But yeah, it shouldn't need it in general, as you're using the share target time, and submitted hashes. 00:55:48 "We lock you out during the set." thats the pool max target setting, not block diff. 00:55:56 Yeah, which is always less than block diff. 00:56:09 Unless network diff drops to sub 500k. 00:56:39 hmmm 00:56:42 Auctually, I think it's still 20-30k in the default config, haven't looked at that in forever. 00:57:11 So you could, in theory, if the math was extra screwball in your code, send a diff target > the current block target. 00:57:24 so much worsds, and no explicit answer yes or no 00:57:26 But the overall of that code tells me it's not likely to happen. 00:57:31 that's why i don't spend time of pull requests 00:58:47 My instinct says "No, you're not going to send a target > block diff." just because you're using the client hashrate to determine the target. 00:59:07 It is, /technically/ a possibility, but it's one I don't see happening any time soon. 00:59:22 1st time use and it's just happened to me on testnet 00:59:48 Sure, and that makes sense, as your hashrate is far exceeding the network difficulty on testnet. 01:00:15 another ting for plug&play: data-dir for lmdb is missing and will tigger assert in code 01:03:31 ^ thanks. I see the issue there. if supplied path doesn't exist 01:04:43 few typos in strings are not important at all 01:05:44 yeah I have a couple of commits waiting to push with a typo or tow 01:05:52 ;) 01:10:09 If someone will double spend monero then it must not be done on weekends. 01:11:17 I've just push the commits I had sitting. If there's a typo I have missed let me know please. 01:25:50 at first glance memory footprint of your pool is the best 02:33:02 cohcho: https://github.com/jtgrassie/monero-pool/commit/e3e133f1d3b375acc1829b9b1e6dbc51f46474ac 02:33:09 thanks 02:34:19 ^ +Snipa 03:10:50 Shiny. 13:28:38 1 gigahash 13:28:51 total miners 26292 13:45:24 wow. the electric bill is a lot lower this month! 16:46:34 heh, is it? gingeropolous. 16:46:36 how comes. 18:04:55 most of the GPUs are off I guess. and I didn't get everything online at once for randomx...