04:58:21 How to make methamphetamine? 05:00:25 Tor is kinda centralized. Way more than it should be. Majority relays are in germany. You can't be a directory authority without identifying yourself which is concerning. 05:43:05 thats why i use mullvad 06:58:58 same here +/- made half in PPLNS of what I paid 07:18:33 the other asshole breaks even 08:46:36 For P2Pool I can't seem to find numbers on the share difficulty, does anyone know where I can find it? 09:21:40 You can find it by running P2Pool and checking the logs. But the easy way is to multiply hashrate by 10 for p2pool-main/mini, and by 30 for p2pool-nano 11:30:41 what would happen if large pools start submitting hash into p2pool rather than mining directly? 11:30:43 would doing this reduce their reward or disadvantage them in any way? 13:15:04 they will be neither advantaged nor disadvantaged... the payout will always be proportional to their hash rates (especially true for large hash rates) 13:20:10 the reason a 51% attacker can force orphan blocks is because they can continue building a private chain with bigger cumulative diff, right? 13:21:17 from what I remember, cumulative difficulty is calculated as the summation of how much difficulty blocks had to overcome 13:22:16 when it comes to choosing the canonical chain, why not switch to the summation of individual blocks' difficulty? 13:22:49 for example, current network hash rate is 5 13:23:23 *5.5 GH/s, so blocks will have to overcome 5.5G * 120 difficulty 13:24:01 however, each block can actually have difficulty quality of much higher 13:35:00 basically, the canonical chain would be: chain with highest cumulative difficulty + lowest sum of PoW hashes 14:31:42 for a 51% attack, one must have the cumulative hashrate divided by 1.9 14:31:43 it's not easy because your hashrate also grows the total hashrate 14:33:37 not really 14:33:39 the 51% attacker can build a private chian, and only expose 1-2 blocks at a time to drop blocks from other miners 14:33:41 thus, he can do it without increasing the difficulty 14:34:22 if now the HR is 5GH/s, to get to 2.6GH you're adding to the 5 and so it scales becoming 7.6GH/s of which you need 4GH/s to attack so forth 14:35:00 you're right, b/c they can selfish-mine and hide the blocks 14:37:43 maybe a solution could be having a p2pool-style share-chain directly in the consensus protocol 14:38:23 fyi, you can also 51% p2pool 14:38:42 think of p2pool as just another monero chain but with shorter block time 14:38:45 you cannot hide blocks from p2pool 14:42:44 controlling the p2pool sharechain is irrelevant for an attack 14:44:12 you find a share, publish it to the network 14:44:13 build a private chain of shares 14:44:15 every time someone else finds a share, publish your own... you either get uncle'd or uncle other miners' shares 14:44:17 hmm... so it depends on how uncle is decided 14:44:45 I totally forgot how uncle is decided... whether it's "first come, first served" or whichever share is better quality 15:01:12 even if you uncle other miners and get most of the reward, you still cannot attack the main chain and orphan blocks 15:01:13 alright, you've 51%'ed the p2pool and getting most of the rewards but that's it, right? 15:02:52 so basically p2pool is free from the same disadvantages 51% attacks have? 15:03:04 why not just force all mining to be from p2pool? 15:03:10 via consenus 15:05:40 . 15:11:12 oh wait i forgot you suggested that 15:11:23 i didn't scroll up sorry (my terminal is small)