03:49:08 narf: monero is the best, which means it's fairly good but not great 03:49:27 right 10:32:56 I'd like to know how much time it'll take for the monero daemon to sync the blockchain, (from start), with a Internet connection of about 24.07 Mbit (download) and 65.80 Mbit (upload) 10:33:27 ^ note: in theory the monerod says I am using a hdd when I am in theory using a ssd 10:42:58 You could get an Internet connection of about 24.07 Mbit (download) and 65.80 Mbit (upload), and measure it. 10:43:31 That said, usually internet speeds aren't the bottleneck. 10:44:16 Disk random access typically is. Spinning disks are atrocious, and syncing will take days with one of these. 11:10:03 Am I still able to send a transaction if my node is still 3 months behind and syncing? 11:15:18 Yes, in theory but (1) the daemon might reject it and (2) the fake outs will be old, which will leak out the fact the tx is either old or made with a partway synced daemon. Not a big problem I guess. 11:15:43 As a side effect, it'll leak that the real spend is at least 3 months old. 11:19:22 None of those a really a massive deal breaker, but on balance I could wait another 3 days for the node to finish syncing before making the transaction. 11:21:05 I really should look at setting up a graphana dashboard to monitor my node, does anyone have any templates? 11:22:28 Nevermind - found this: https://www.reddit.com/r/Monero/comments/nz7ysc/dashboards_with_monero_metrics/ 11:30:47 3 days for 3 months ? Wheee. 11:32:48 yeah, its basically taking a day to sync a month. Good ol rust drives 16:51:08 moneromooo: I am having a larger problem, the issue is that when I order my init system to kill the daemon that runs monero, the daemon is killed but the monero process is kept at uninterruptible process type, (which makes me not be able to run other monerod instances) 16:52:58 AFAIK, that means stuck in kernel space, so a kernel bug or stuck waiting on I/O on bad HW. 16:53:38 If you can get a stack trace, it might shed some light. 16:55:00 ^ I'd have to get one of the processes, and I have 4 to pick, in which should I attach gdb? 16:55:30 ^ what, they just disappeared 16:55:54 ^ well, better for me (ig) 16:57:25 moneromooo: also, (completly unrelated), but if I started mining monero on some pool let's say pool x, I can use a subaddress for pool x and another address for pool y right?, except that apparently P2Pool doesn't allow me to run the daemon without specifing a main addr... 16:58:20 You can't mine to subaddresses. It's not supported. 16:58:36 oh, so I lost those coins completly? 16:58:57 well, they wheren't much so idc.. 16:59:06 You mean you gave a pool a subaddress, and it did not complain, but just accept? 16:59:24 rbrunner: yeah, if you want I can say the pool name 16:59:56 Hmm, yes, of course a pool can pay you out to a subbaddress. I was talking about solo-mining. 17:00:05 Yes. 17:00:27 And p2pool is technically something like solo mining. 17:01:02 what's the difference between solo-mining and pool mining? (I asume pool mining uses the normal way of transfering money in monero?) 17:02:04 With pool mining you only submit "shares". With solo mining you submit a block - if you can find one, of course. 17:02:04 so if p2pool is like solo mining even if I mine normally I'd only get paid less? how can that be then? 17:02:10 Solo mining is, you solve a template your daemon made to your address. Pool mining is, you solve a template the pool's daemon made to its own address. 17:02:28 And you trust hte pool to send you some monero back to thank you. 17:02:54 so, a there will be a different challenge even for the same block? 17:05:04 ^ because the template will be different because the daemon will make it different as the template needs to contain the address that the money will go to, (if valid obsly) 17:09:33 The template changes, but the target diff is the same 17:09:55 what does that mean? 17:10:23 The network difficulty determines how much work (on average) is required to find a block 17:10:31 And it's the same for everyone 17:10:44 The difference between solo and pool is that solo is all-or-nothing, while pool pays small amounts more regularly 17:10:53 diff by difficulty not diff by difference 17:10:59 And you submit "shares" to the pool to prove that you are doing work 17:11:28 Yes sorry, in the context of mining "diff" means mining difficulty 17:11:57 ^ no problem, I should have alredy knew that :P 17:12:02 (And those shares are what get you paid) 17:13:20 P2pool is a little special, because there is no trusted middleman - but at the end of the day it's still pool mining 17:16:07 so everyone needs to "review" your blocks if they made a proper block?, wouldn't that take soo much time that the block would get invalid by then? 17:16:23 ^ (like a valid block but outside of the time window) 17:17:31 just one p2pool node checks the block validity. then it submits it to mainnet if it's good 17:18:06 and the idea of sending the money to the other users, or is it sent to a special address? 17:19:24 P2pool blocks are constructed in such a way that every p2pool user gets their share of the block reward (according to their contributions) 17:20:03 so blocks need to be constructing a transtation with the block reward inside of it? 17:20:17 all blocks do that 17:20:21 ^ but then how come that subaddrs aren't allowed? 17:20:49 just because. subaddrs were invented later, the encoding isn't supported for coinbase txns 17:20:51 Because the mining protocol dictates that rewards can only be sent to the primary address 17:21:21 thanks for the info 17:21:30 technically subaddresses are possible in coinbase txs 17:21:52 but they'll double the size of coinbase outputs 17:22:29 and there's no code written yet that can do it (neither in monerod nor in p2pool) 17:26:28 https://github.com/monero-project/monero/pull/3839 17:27:04 From the long and dark history of unmerged Monero PRs :) 17:27:22 right 17:29:09 looks like the changes weren't worth the bother 17:29:53 each subaddress requires a separate tx pubkey, this is why I didn't add support to p2pool - it add 32+1 bytes per output, almost double the size 17:30:49 also the wallet2 scanning is written in such a way that it will be O(N^2) if everyone in p2pool mines to subaddress 17:31:14 each of N outputs will scan all N pubkeys until it finds the right one 17:33:44 actually no, it's sorted by output index. But still, 2x transaction size is not worth it 17:39:18 sech1: there's a zmq related PR open, could you take a look? 17:39:54 ah, we discussed it with jberman before. I'll take a look 17:45:54 ^ didn't even knew that by making a questionary about how pool mining works i'd indirectly make a PR be seen again back :P 21:02:08 hello