01:29:06 Ok yup denominations. So really sech1 your p2pool mining took advantage of an old feature of the codebase and used 01:29:13 It in a new creative way? 05:18:02 Hey one question: is p2pool more or less efficient than the traditional pool mining on low hashrate (lower than 1kh)? Will it manage to find same amount of shares? Or will it find them less frequently but they will be worth more? 05:55:42 It will find fewer shares, but each share will result in a payout. In the long run it will be a bit higher profitability because of 0 fees and more efficient block propagation (fewer Monero orphan blocks). 05:56:11 also Monero blocks in p2pool sometimes will have more transaction fees included because p2pool uses better picking algorithm 09:36:24 Third block found: https://xmrchain.net/block/2438316 10:43:47 cool, so lower hashrate will work just fine? And also one more thing - can many miners connect to p2pool instance with different usernames/passwords? 11:07:15 low hashrate works just fine 11:07:31 no, each miners needs to run p2pool instance. One p2pool instance = 1 wallet address 11:08:00 they all can still connect to the same Monero node if someone makes it available 11:51:11 BLOCK ACCEPTED at height 2438400 11:51:41 That's #4 11:52:27 nice 11:53:11 my single p2pool share I found this morning resulted in 2 ~0.0004 XMR payouts so far, nice 11:53:41 Double spend detected! :D 11:54:37 I'm wondering if there's an api to get the p2ppool stats like the blocks found and it's hashrate 11:56:28 actually no, 3rd block was found before I found my share, so I got only one 0.000420419537 XMR payout 11:57:34 no api yet 11:57:48 you can run "status" command in p2pool console 11:58:02 i assume that two of the coinbase outputs https://xmrchain.net/tx/c7de62c65a67c180f2169172a6d6cd77531bed72d0dc9090044eed74bdb6d2e4 were for single shares, why do they have different amounts 11:58:16 https://paste.debian.net/hidden/dc8ea922/ 11:58:34 payout for share depends on share difficulty 11:58:47 ok thanks 12:02:11 will there ever be a "remote node" for p2pool so that users don't have to download the blockchain and setup the p2pool node and everything? 12:13:14 read my message from 1 hour earlier 12:13:30 ah, you didn't see it 12:13:40 no, each miners needs to run p2pool instance. One p2pool instance = 1 wallet address 12:13:41 they all can still connect to the same Monero node if someone makes it available 13:05:44 Does p2pool require full sync blockchain or does it work with pruned blockchain? 13:10:46 p2pool on my dev PC works with pruned blockchain 13:13:25 Ok thanks. 13:49:07 Does p2pool need to have access to the wallet file or is the wallet address enough like with solo mining? 13:53:41 just address 13:54:13 it only needs to know your payment address for your payouts, nothing more 13:55:45 so i still have 7 peers, is that right? 13:56:09 same here 13:56:29 and we have 28MH 13:57:08 1% of network 13:57:29 That's pretty damn good given it's just started. Congrats :) 14:00:58 and I have 2 shares in PPLNS window now, yay 14:03:07 i have zero :P 14:03:29 3 phones just aren't gonna cut it :D 14:19:47 so once you drop below a certain percentage of network hashrate, your odds of hitting are essentially zero 14:27:08 --addpeers does nothing for startup parameter, had to run addpeers manually inside p2pool cli, got no connections until I connected manually. 14:31:42 hyc less than 0.1% of p2pool hashrate and you'll be getting pool shares only once in a while, but it's not a problem. It's like solo mining, but with smaller difficulty 14:32:22 --addpeers works, what exactly did you try to put there? 14:32:42 --addpeers 65.21.227.114:37890 14:32:49 copypasted the whole example command from github 14:33:31 try to add --loglevel 5 to the command line and check what p2pool says when it starts 14:34:34 do i need to delete the p2pool_peers.txt or anything else so none of the peers are read from cache 14:34:56 yes, delete it 14:37:22 2021-08-30 14:36:03.4254 P2PServer connecting to 65.21.227.114:37890 | Connections = 0 (0 incoming) 14:37:55 P2PServer status 14:37:55 Connections = 0 (0 incoming) 14:38:37 still nothing 14:39:40 http://192.168.1.156:3520/file/1/hh9KrM4UUckGYKA8 14:39:52 ooff.. god damn copy paste 14:39:57 lol 14:40:10 http:/file/1/hh9KrM4UUckGYKA8 14:40:22 did you open an inbound port in your firewall? 14:40:30 yes 14:40:34 of course the outbound connections still should have worked 14:40:42 just let me copypaste more 14:40:48 once I got it sorted :D 14:40:57 2021-08-30 14:39:27.2431 P2PServer new connection to 65.21.227.114:37890 14:41:01 2021-08-30 14:39:27.2431 P2PServer sending HANDSHAKE_CHALLENGE 14:41:05 I'm surprised right now I have 0 incoming, all outgoing 14:41:07 2021-08-30 14:39:27.2431 P2PServer peer 65.21.227.114:37890 sent HANDSHAKE_CHALLENGE 14:41:15 2021-08-30 14:39:27.2432 P2PServer peer 65.21.227.114:37890 disconnected 14:41:20 2021-08-30 14:39:27.2434 P2PServer peer list saved (0 peers) 14:41:30 sounds like that peer doesn't like you 14:41:37 you might have failed too many times and got banned 14:41:41 WARNING 2021-08-30 14:39:23.4292 P2PServer peer 84.240.124.114:58430 has been idle for 6 seconds, disconnecting 14:41:42 naw, once i add it inside the console it connects instantly 14:41:46 this is what I see 14:42:11 see? 14:42:18 bam, and it connects 14:42:22 my node didn't get HADNSHAKE_CHALLENGE & HADNSHAKE_SOLUTION messages from your node 14:42:38 so it decided it was some random port scan and disconnected after 6 seconds 14:42:56 weird, why it works once I run addpeers ip:port 14:43:24 it just tries to connect again 14:43:54 it's running through all the blocks 14:44:37 let it sync up then 14:44:44 do you want full log output with the problem? 14:48:57 hmm, I already see what went wrong. Your log says that my node disconnected immediately, but it didn't disconnect on my side. 14:49:21 so it tries to connect once and gives up? 14:49:35 so something in between broke connection 14:50:14 it connects once, yes 14:50:31 Does Hugepages have any role causing this issue? I got them disabled atm. 14:50:37 sounds suspicious. an immediate break means an active RSt packet or somesuch. a timeout would take much longer 14:53:32 maybe his provider has DPI which triggered 14:53:42 or router acting up 14:53:56 ah hey you might be right 14:54:02 lemme test something 14:54:11 whatever, I need to do more than 1 attempt to connect to a peer when it's added 14:55:22 WARNING 2021-08-30 14:43:17.5560 P2PServer got a request for block with id 2dc98048a49024abae57172becce52d8510844d4256ffd31b1f80a230272afb0 but couldn't find it 14:55:32 ? 14:56:16 hmm.. stopped ntopng, the connection worked once, restarted the p2pool and now it won't connect again. 14:57:28 so no, ntopng had nothing to do with it 14:57:32 gingeropolous try to grep your logs for this block id 14:57:34 and got no dpi enabled on router 14:57:44 monerod or p2pool 14:57:51 p2pool 14:58:50 sech1, https://paste.debian.net/hidden/fe0723a1/ 14:59:23 p2pool diff is already 2x yesterday's, 288M vs 140M 14:59:39 itshappening.gif 15:00:02 gingeropolous that's ok. Some node broadcasted a block that referenced this id, and everyone started asking for this id until they synced 15:00:56 ah, i also had this series of errors sech1 : https://paste.debian.net/hidden/827279f3/ , but afaict everythings fine now 15:01:35 a status: OK line on status would be cool, but dunno how it could be self aware to that extent 15:01:59 lol what does not OK mean 15:03:21 i dunno. can't talk to other nodes, miners asking for pizza, ... just a summary of everythings fine, vs not ok meaning somethings weird, vs. borked meaning this needs some serious help. yah know, green, yellow, red 15:04:23 i guess i should eventually check this mining wallet 15:05:42 I've earned about 12 cents. gonna have to look up my electricity price 15:08:36 Improved status command: https://paste.debian.net/hidden/3883dd44/ 15:08:58 mining with custom fixed diff on my machines, so stratum server can estimate hashrate better now 15:10:11 if you're using fixed diff, would be useful for status to display current diff 15:10:23 it's fixed diff per miner 15:10:28 in config.json 15:10:54 yes, even so. 15:10:57 for example "user": "x+265000", in config.json for Ryzen 5600X 15:11:26 how can I display current diff if I have 5 different values from 5 different computers? 15:11:40 current p2pool diff? 15:11:52 it's side chain hashrate * 10 15:11:59 ok 16:25:21 Just reading the 'How to test' guide on github, will everything still work if I prune the blockchain? 16:25:52 yes 16:26:40 Thanks :) 17:32:15 Just a thought, won't the difficulty raise too much once then side chain hashrate increase above certain rate? 17:42:16 It should rise just right. What makes you think it might rise too much ? 17:43:04 define "too much" 17:45:54 Hmm, well there is not really upper limit, it just becomes super rare to actually send share that is above the diff :P 17:47:34 still a walk in the park compared to solo mining 17:48:10 true 17:50:17 D: that block found ascii 17:52:20 thank :D 17:52:23 *thanks :D 17:53:15 block #5 if I count right: https://xmrchain.net/block/2438575 18:05:41 gah, wheres the asci 18:08:08 https://paste.debian.net/hidden/f07c77e2/ 19:48:03 wen release? 19:48:22 next release won't contain all changes necessary for p2pool 19:54:48 yet it works now? 19:55:48 custom build of monerod 20:10:43 so you need a special monerod until it gets mainlined? 20:11:28 yes