04:45:31 <QuickBASIC> Im pretty sure old solutions are accepted and mined as uncles up to 3 blocks deep, DataHoarder. I remember sech1 talking about it. Unless you're talking about something else as uncle uncles.
04:48:41 <gingeropolous> mining banter
09:42:35 <mechanic41turk[m> sech1: nice interview on MoneroTalk. Pretty interesting project, hoping it grows.
09:43:08 <mechanic41turk[m> btw, would you put the QR-code next to the donation address for the project? Would make easier to send a few bucks on the fly using a mobile wallet.
09:51:46 <pauliouk> Looks like I can only land shares overnight heh
10:01:22 <sech1> mechanic41turk you can click the donation address on p2pool.io and it will open your wallet, or you can just copy-paste it on github
10:01:56 <mechanic41turk[m> sech1: yeah, I will need to visit the page on my phone though
10:02:10 <mechanic41turk[m> I am looking at p2pool.io on my laptop and my wallet is on my phone.
10:02:49 <sech1> there's no space for QR code there though, it will litter the page
10:05:06 <mechanic41turk[m> ok, you are the boss ;)
11:36:54 <xmrvsbeast[m]> BLOCK ACCEPTED at height 2447745 and difficulty = 336764038166
11:36:55 <xmrvsbeast[m]> 100 blocks mined!
11:41:24 <DataHoarder> QuickBASIC: as in, when a block is accounted as uncle it does not look further into it for more uncles
11:41:50 <DataHoarder> They get added next to it if anything 
12:41:27 <garth> Xmrvsbeast[m]: BEAST
12:56:53 <mightysnowman> was very interesting interview
12:57:12 <mightysnowman> the interviewer seemed a bit annoying with the repeditive "will you add any fees?" questions
13:09:16 <nioc> Well he has a constant moving banner for the entire time about donating to monerotalk, advertised his CCS at the beginning which has since been filled, $70k for 6 months o_0
13:11:16 <hyc> it's an eternal problem. tech-savvy people are busy doing tech, not interviewing others
13:11:30 <hyc> so the people doing interviews ... rarely understand any of the relevant topics
13:12:07 <hyc> all they understand is price/cost/fees/etc
13:29:05 <nioc> Does p2pool work with merge mining?
13:44:52 <mightysnowman> are there yet any mobile wallets that can show p2pool payouts?
13:47:25 <hyc> yes
13:47:31 <hyc> monerujo updated already
13:47:31 <DataHoarder> Moneroju afaik
13:47:46 <DataHoarder> switched letters heh
14:02:59 <pauliouk> go on then, I'll watch the MoneroTalk - who forgot to turn notifications off on their phone? :D
14:08:18 <pauliouk> So, as the hashrate of p2pool increases, does that reduce the likelihood of landing a share if you have a low hashrate? Or does the luck chance remain the same?
14:13:20 <pauliouk> nevermind, just got to that part of the talk. Would be good to see p2pool-industrial and p2pool-lite
14:15:55 <Hisha> had a bunch of WARNING 2021-09-12 14:00:15.4174 SideChain add_external_block: block is built on top of an unknown mainchain block a2e977bb115139dc11ec6d1df2bf28e7250d04694c2be79437ca8aded3092c56, mainchain reorg might've happened over night is there something I need to do or something that will clear up?
14:19:58 <DataHoarder> should catch up as long as you are getting blocks from monerod Hisha 
14:20:26 <DataHoarder> if it keeps going for a while, either you or a p2pool peer has desynced
14:21:43 <Hisha> noticed I missed out on the last 2 blocks and had no recent shares so I rebooted and restarted both monerod and p2pool so hopefully fixes that
14:22:14 <CzarekNakamoto[m> if I get the code correctly if enough people will change their config.json... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/2ab86323c6db52e23cac4e869b95db3a6273da3e)
14:26:53 <CzarekNakamoto[m> or changing pplns_window to, let's say 6k and mining on 2 chains at once? would that work?
14:28:53 <DataHoarder> that won't do much CzarekNakamoto[m as it will place you into another sidechain
14:29:06 <DataHoarder> and you will not get rewards or hashrate from main one
14:29:27 <CzarekNakamoto[m> But if half of the hashrate go to one chain and half to the other?
14:29:31 <DataHoarder> window = number of shares ~= number of total possible outputs
14:29:48 <DataHoarder> if you increase window too much it just creates more outputs
14:29:59 <DataHoarder> and less space for actual monero transactions
14:30:19 <DataHoarder> changing time just shortens window or increases it for same share count
14:30:19 <CzarekNakamoto[m> ah right.. how about adjusting the block_time?
14:30:28 <CzarekNakamoto[m> (sorry for asking dumb quesiton)
14:30:33 <DataHoarder> that just denotes how long in hours the window is, on average
14:30:44 <DataHoarder> it's a chain that self-adjusts
14:30:50 <CzarekNakamoto[m> will that affect the difficulty?
14:30:53 <DataHoarder> so all that matters is actual hashrate
14:31:07 <DataHoarder> more miners = more difficulty, less miners = less difficulty
14:31:11 <DataHoarder> all that matters
14:31:20 <DataHoarder> less miners ofc also means less blocks found on-chain
14:31:25 <DataHoarder> so you will get paid less
14:32:23 <DataHoarder> it will not be "Easier"
14:32:34 <CzarekNakamoto[m> Hm okay
14:32:45 <DataHoarder> as you will then get main chain blocks according to how much total hashrate you have
14:33:24 <CzarekNakamoto[m> Also, what will happen when everybody switch to p2pool mining?
14:33:31 <DataHoarder> creating an alternate one for lower hashrate ones might be fine, leave parameters as is and just set a password
14:33:34 <CzarekNakamoto[m> wouldn't that make diff much higher?
14:33:37 <DataHoarder> in the end if you ever find a share
14:33:41 <DataHoarder> and everyone is in p2pool
14:33:58 <DataHoarder> that share will give you payouts for about 6h every ~2m
14:34:29 <DataHoarder> cause as p2pool hashrate increases also number of mainchain payouts increases accordingly, on average
14:36:19 <CzarekNakamoto[m> But monero block time is 2 minutes, right? and if we assume that every block is found by p2pool, it will mean that only 12 p2pool block were mined in the window between blocks, right?
14:36:20 <DataHoarder> vs a sidechain for lower hashrate that might find blocks on average each ~6h, you will get for each share you find about one on average
14:36:49 <DataHoarder> yes CzarekNakamoto[m but shares keep counting even if a block is found
14:37:08 <DataHoarder> all your shares (and uncles) for 2160 sidechain blocks
14:37:26 <DataHoarder> one share can give many payouts across the whole window
14:37:54 <CzarekNakamoto[m> so for one share I would get many payouts if the blocks were found fast enough?
14:37:56 <DataHoarder> (or none, if p2pool chain finds no mainchain blocks)
14:38:09 <DataHoarder> if the "mainchain" blocks were found fast enough yes
14:38:22 <DataHoarder> so, higher p2pool hashrate = more main chain blocks found
14:38:28 <pauliouk> I found one share last night and got 3 payouts, so it balances out nicely
14:39:16 <CzarekNakamoto[m> That would mean that I'd get much higher reward but less often
14:39:50 <DataHoarder> as mentioned, it averages out
14:40:11 <DataHoarder> while if you make a small p2pool you might get many shares, but no payouts in a long time
14:40:46 <CzarekNakamoto[m> solo mining also averages out, but for somebody with a laptop and 3khs it may take ages to find a block
14:41:11 <DataHoarder> yep, think of this as solo mining with higher chance to get a payout
14:42:03 <CzarekNakamoto[m> So the probability of getting one payout is solo/2160? Right?
14:42:18 <DataHoarder> not excactly, that would be if everyone was on p2pool
14:42:25 <DataHoarder> look at current hashrate of p2pool
14:42:49 <DataHoarder> can't do the math atm,
14:43:37 <CzarekNakamoto[m> hm okay! Thank you very much! I'll try to figure things on the go ;p. Thanks!
14:45:03 <Hisha> wasn't there a entry for your hashrate between these two lines in status or was that removed? Side chain hashrate       = 56.719 MH/s
14:45:03 <Hisha> PPLNS window              = 2160 blocks (+87 uncles, 0 orphans)
14:45:41 <DataHoarder> Side chain hashrate       = 56.935 MH/s
14:45:41 <DataHoarder> Your hashrate (pool-side) = 223.738 KH/s
14:45:41 <DataHoarder> PPLNS window              = 2160 blocks (+87 uncles, 5 orphans)
14:45:50 <DataHoarder> do you have shares found Hisha ?
14:46:01 <Hisha> hmm not showing for me anymore
14:46:18 <Hisha> no shares currently so maybe that's it?
14:46:21 <DataHoarder> yep
14:46:27 <DataHoarder> > (hashrate_est ? "\nYour hashrate (pool-side) = " : "") << (hashrate_est ? log::Hashrate(hashrate_est) : log::Hashrate()) <<
14:46:33 <DataHoarder> it's hidden if no shares
14:46:42 <DataHoarder> same as the position indicators
14:46:52 <Hisha> oh ok
14:47:36 <Hisha> guess my luck just sucks today
14:54:16 <Inge> hm. running on a 4GB vps might be pushing it...
14:54:18 <Inge>               total        used        free      shared  buff/cache   available
14:54:22 <Inge> Mem:           3942        3557          93           0         291         174
14:58:38 <Inge> this "your shares position" view, where can I see it?
14:59:22 <DataHoarder> Inge: once you find a share, it will show up when you execute "status"
15:01:40 <Inge> it says Shares found       = 3
15:01:44 <Inge> are those shares I found?
15:02:08 <DataHoarder> yes, but probably during first sync at lower difficulty, so they don't count towards current PPLNS window Inge 
15:02:18 <DataHoarder> look at "Your shares" instead of "Shares found"
15:02:21 <Inge> that makes sense
15:04:30 <jaska087> Inge you could run the p2pool in light mode to reduce memory usage
15:09:41 <Inge> What are the downsides?
15:09:51 <QuickBASIC> Inge if you grep "SHARES FOUND" p2pool.log you can see the shares you've found if the diff is really low they're "fake" shares from the sync.
15:10:07 <DataHoarder> slower pow check time Inge but you won't be checking many per second
15:11:25 <Inge> I could just host p2pool somewhere else - it was just easy to set it up on the vps :D
15:12:24 <Inge> does it make much diff whether or not the p2p port is exposed to the internet?
15:14:20 <DataHoarder> better syncing with others as they can use you for connections
15:20:24 <Inge> ack
15:59:40 <wssh> so basic question. 
16:00:13 <wssh> even though we run our own pool with our own workers, the load is still shared on blocks by other nodes?
16:00:38 <wssh> because my measly 3 kh/s haven't paid anything out.
16:00:48 <wssh> and it's been running for 4 days.
16:02:32 <wssh> -- so for now i've set it to use xmrvsbeasts test node, and set xmrig on localhost mining.
16:03:03 <wssh> maybe i'm lacking something.
16:09:06 <QuickBASIC> You could just be unlucky. I'm running a similar hashrate (4kh/s average) and haven't got anything for a few days. wssh
16:09:29 <wssh> QuickBASIC: but you have gotten something, correct?
16:10:00 <QuickBASIC> Yeah, but it was when the diff was a bit lower.
16:10:39 <wssh> i'm setting a pool diff of 10033 because if i don't, i don't get any shares, period.
16:12:07 <wssh> also the wallet adress i'm using is not on the server i'm running the software from, it's the gui wallet on a seperate machine, so i assume that's fine.
16:12:30 <jaska087> As long its not sub address or integrated address, it doesn't matter
16:12:34 <QuickBASIC> You mean on your miner with xmrig -u x+10033, right? That won't change how often you get payouts, just make stratum stats more accurate.
16:13:48 <QuickBASIC> wssh, just checking, you didn't change anything in config.json right?
16:22:52 <DataHoarder> wssh: changing difficulty doesn't "give" more shares, remember, you are mining a sidechain
16:23:17 <DataHoarder> don't change config.json, that creates your own sidechain and you don't share any hashrate with others, basically you are solomining
16:26:09 <wssh> i did not change config.json and yes QuickBASIC that command for xmrig exactly.
16:27:44 <QuickBASIC> wssh Perfect just checking to be sure. You're probably just unlucky. That hr should get you 1 share every 72 hours or so.
16:27:59 <wssh> and as for the wallet inquery; it is the primary address in the wallet gui from getmonero.org.
16:28:32 <DataHoarder> just so you know, that will not give more sidechain shares wssh, just get better hashrate reporting
16:28:42 <DataHoarder> and yes you don't need any wallet configured on monerod
16:28:50 <DataHoarder> just have an address on p2pool
16:29:07 <wssh> everything is running locally. :)
16:29:25 <wssh> well, except now i'm running on xmrvsbeast test node.
16:32:17 <wssh> curently running on 2 of these.
16:32:19 <wssh> Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz
16:32:26 <wssh> with 48 gb ram.
16:32:26 <DataHoarder> v0s, sad
16:32:32 <DataHoarder> DDR3 I guess?
16:32:35 <wssh> yes.
16:37:23 <wssh> it is a nice 	Product Name: PowerEdge T620
16:37:28 <wssh> :)
16:37:47 <wssh> bit old, but hey i got it for $30
16:38:05 <wssh> and since then have mined 30 in XMR with it.
17:02:33 <EDad> Hello! Does this channel have logs? I'd like to dive in to past discussions about p2pool before possibly asking questions that have been answered before.  Link if possible? Thanks!
17:05:12 <CzarekNakamoto[m> on matrix.org #monero-pow:libera.chat iirc
17:05:18 <DataHoarder> EDad: https://libera.monerologs.net/monero-pow/20210912
17:05:24 <DataHoarder> no need to have Matrix
17:06:00 <EDad> Perfect guys! I'll be back I'm sure. I've got some catching up to do.  Cheers!
17:07:16 <CzarekNakamoto[m> right
17:07:51 <Hisha> still getting WARNING 2021-09-12 17:07:12.2232 SideChain add_external_block: block is built on top of an unknown mainchain block cf280d789367b5093e5a93e9d6d9e254951564874d111506b3648f6e2c4e039d, mainchain reorg might've happened
17:09:53 <nioc> Mining reward = your hr/network and it all averages out no matter what.  The problem is that almost all miners have a relatively low hr so variance makes it necessary to use a pool.  
17:10:47 <nioc> p2pool is a decentralized pool with more frequent and smaller payouts
17:11:13 <Inge> Better to get a dollar a day than to mine for a year with no payment
17:11:41 <nioc> Inge: r u using the internet?
17:11:50 <Inge> what's the internet?
17:13:00 <nioc> More and smaller sounds like less variance 
17:13:01 <DataHoarder> how many Hisha / how often
17:13:36 <Hisha> that came about an hour after the last one
17:13:42 <DataHoarder> ignore
17:13:43 <nioc> Inge: it's a matter of debate
17:13:47 <DataHoarder> it will just happen
17:14:00 <DataHoarder> sometimes you get blocks later than other peers
17:14:47 <Hisha> at 100k h/r I should be getting some shares, haven't gotten anything but that for half a day at this point
17:15:16 <DataHoarder> what is your full output of "Status"
17:15:20 <DataHoarder> status*
17:15:39 <Hisha> 2021-09-12 17:15:27.7518 SideChain status
17:15:40 <Hisha> Main chain height         = 2447940
17:15:40 <Hisha> Main chain hashrate       = 2.896 GH/s
17:15:40 <Hisha> Side chain height         = 105442
17:15:40 <Hisha> Side chain hashrate       = 60.742 MH/s
17:15:40 <Hisha> PPLNS window              = 2160 blocks (+83 uncles, 0 orphans)
17:15:42 <Hisha> Your shares               = 0 blocks (+0 uncles, 0 orphans)
17:15:44 <Hisha> Block reward share        = 0.000% (0.000000000000 XMR)
17:15:46 <Hisha> 2021-09-12 17:15:27.7519 StratumServer status
17:15:48 <Hisha> Hashrate (15m est) = 115.012 KH/s
17:15:50 <Hisha> Hashrate (1h  est) = 110.782 KH/s
17:15:52 <Hisha> Hashrate (24h est) = 112.536 KH/s
17:15:54 <Hisha> Total hashes       = 471300831
17:15:56 <Hisha> Shares found       = 16
17:15:58 <Hisha> Average effort     = 61.979%
17:16:00 <Hisha> Current effort     = 75.986%
17:16:02 <Hisha> Connections        = 26 (26 incoming)
17:16:06 <Hisha> 2021-09-12 17:15:27.7519 P2PServer status
17:16:08 <Hisha> Connections    = 11 (3 incoming)
17:16:10 <Hisha> Peer list size = 154
17:16:12 <Hisha> 2021-09-12 17:15:27.7519 Util no background jobs running
17:16:18 <DataHoarder> well that is indeed the full output :)
17:16:27 <DataHoarder> maybe can use a paste site next time
17:16:41 <DataHoarder> hmm, you have set custom difficulty on stratum right?
17:16:49 <DataHoarder> like user 'x+100000' or alike
17:17:07 <Hisha> yeah think I'm at 500k
17:17:30 <DataHoarder> do you have any "SHARE FOUND" on logs?
17:17:47 <Hisha> not today
17:17:50 <DataHoarder> you can use https://paste.debian.net/ for large amounts
17:18:54 <DataHoarder> given you have avg effort lower than current effort you might have gotten some
17:20:29 <Hisha> https://paste.debian.net/1211504/
17:21:03 <DataHoarder> I only see three valid there
17:21:27 <DataHoarder> and you have restarted p2pool a few times, I guess, to get those extra shares
17:21:50 <Hisha> yeah restarted a few times and even reinstalled monerod
17:21:52 <DataHoarder> 30-32 are the good shares)
17:22:07 <DataHoarder> > 0.983%
17:22:12 <DataHoarder> "unlucky" :>
17:22:43 <DataHoarder> I don't see anything wrong firsthand, besides you got very unlucky?
17:23:06 <DataHoarder> you see regular "P2Pool new miner data" entries right?
17:23:18 <DataHoarder> or "P2Pool new main chain block"
17:24:21 <Hisha> yes
17:26:25 <URoRRuRRR[m]> Re the difficulty for slow miners - I've set mine based on their hash rate * 30
17:26:55 <URoRRuRRR[m]> Should I not do that and leave the difficulty to be the default?
17:27:11 <DataHoarder> it's fine, you will get some hashrate reporting URoRRuRRR[m] 
17:27:12 <URoRRuRRR[m]> Slow being 2kh or less
17:27:25 <DataHoarder> you don't "have to" but it's nice to see report on p2pool
17:27:36 <DataHoarder> default would be, not report anything but matching shares
17:29:45 <URoRRuRRR[m]> Got it, thanks DataHoarder 
17:46:36 <mightysnowman[m]> ah yes, magic smoke for 0.01xmr, worth it
17:46:49 <mightysnowman[m]> something got cooked, not yet sure what
18:39:31 <DataHoarder> alright, let's see if bot works for notifying new blocks, maybe in a few hours?
18:56:09 <pauliouk> finally :) landed a share while I'm awake :D
18:57:40 <Inge> pauliouk: what hashrate are you running?
18:57:57 <pauliouk> at best, 7Kh/s
18:58:17 <pauliouk> average ~6500h/s
18:59:01 <URoRRuRRR[m]> pauliouk same for me and I got my first share this morning :)
18:59:47 <pauliouk> nice, congratulations URoRRuRRR - hope you're liking the p2pool :)
19:00:48 <pauliouk> in an ideal world I'd love to land about 8 shares in one window, then have someone drop a 1gh/s rented hash botnet onto the node :P
19:02:26 <Inge> still waiting on that first magic share
19:02:49 <pauliouk> whats your hashrate Inge?
19:02:55 <Inge> ~50Kh/s
19:03:37 <pauliouk> should come soon enough, and plenty of them
19:03:37 <URoRRuRRR[m]> I'd be happy with 1 share a day :D... and a pool block every 3 minutes
19:04:41 <pauliouk> it feels like a XMRvrsBeast raffle win when I land a share heh
19:07:31 <EDad> I have 5 machines of various hashrates connected to one instance of p2pool that is working off of my blockchain. Should I be using p2pool for each xmrig instead? 
19:08:13 <DataHoarder> that's fine
19:08:14 <pauliouk> nope, one p2pool node should be enough
19:08:25 <pauliouk> so long as there's no huge latency between the machines?
19:08:40 <DataHoarder> shouldn't matter much
19:08:43 <DataHoarder> given we have uncles
19:09:18 <pauliouk> true true
19:10:03 <EDad> They are on the same network so latency is 0. My concern is should I set the diff for each machine according to thier capability? And how often should each machine be sending results?
19:11:28 <EDad> Because clearly my little laptop can't work as fast as my better machines. Does p2pool send the same jobs to the varied machines?
19:11:44 <mightysnowman[m]> 30 x their hashrate = difficulty
19:12:10 <mightysnowman[m]> Wont help with p2pool tho, just makes stats better and optimizes your local network usage
19:12:33 <pauliouk> set the difficulties on each xmrig instance
19:14:31 <EDad> Just trying to get my head around all this. Please forgive me :)  I see p2pool sending jobs to 5 clients, and xmrig receiving those jobs right away. But are they the same jobs even if each machine has thier own custom diffs?
19:20:53 <hyc> each client gets unique jobs
19:27:10 <EDad> That was helpful. I'm horrible about being clear in my questions. It seems I have set everything up correctly. But this time in between shares gets my mind racing and wondering if something is wrong or could be improved.
19:28:20 <DataHoarder> lucky-bot will now post new blocks found automatically on #p2pool-log, in addition, you can subscribe to receive notifications when shares are found
19:31:01 <pauliouk> nice work DataHoarder!
19:32:04 <pauliouk> I was tempted to edit the p2pool api code so it'd display the blocks with even more colour, and supress some of the other output. if something wasn't working right, I'd still have to check the logs to see what was up
19:32:25 <DataHoarder> yeah... I went overboard and now it backs stuff to a postgres db
19:32:34 <DataHoarder> and follows reorgs when they happen
19:33:46 <sech1> I didn't get a single share in 36 hours
19:33:51 <sech1> with 8.8 kh/s
19:35:18 <sech1> Current effort     = 201.068%
19:35:20 <hyc> \i haven't either
19:35:22 <pauliouk> ouch sech1. Would have hoped luck would have been more on your side :O
19:35:33 <DataHoarder> might end up making a simple web interface with this later on, so you can track your progress
19:35:37 <DataHoarder> https://github.com/WeebDataHoarder/p2pool-log
19:35:46 <sech1> but yesterday I got 2 shares and 3 blocks paid for them :P
19:36:09 <pauliouk> same this morning for me sech1, 3 payouts from 2 blocks
19:36:23 <hyc> and my mac is still submiting shares with invalid job ids. piece of shit
19:37:04 <EDad> Same, 2 shares 3 blocks yesterday. Nothing since.
19:37:13 <DataHoarder> you can subscribe either by private message to "lucky-bot" or message on #p2pool-log ".subscribe PAYOUT_ADDRESS", would recommend doing this on an alternate nick (reminder again that payout addresses are public in p2pool)
19:37:45 <hyc> 80 uncles, 5 orphans
19:37:54 <hyc> seems to be growing
19:38:40 <DataHoarder> more towards that bot later on, time to prepare for work
19:38:57 <sech1> It's problems with monerod synchronization. Sometimes my node receives new Monero block 10-15 seconds after other nodes. If same happens to XvB's node, it will orphan other p2pool blocks
19:38:57 <DataHoarder> ping me if you have questions about it
19:39:40 <Inge> sech1: 97% effort so far. 
19:41:05 <DataHoarder> this is what a share found looks like  https://irc.gammaspectra.live/22ed5b4fb6063014/image.png  (via DM)
19:41:20 <DataHoarder> uncles are also reported, untested cause I'm waiting for one
19:41:50 <DataHoarder> and if XvB is reading this don't subscribe to this, gets rate limited by libera heh
19:42:30 <hyc> hey, if you're using the logrotate config I pasted here before, need to add either nocompress or delaycompress
19:42:38 <hyc> otherwise it screws up
22:14:39 <drewpeacock> hi everybody
22:52:13 <DataHoarder> an example of the bot reporting blocks found  https://irc.gammaspectra.live/6df7b8409ac35b4d/image.png 
22:55:35 <DataHoarder> hmm https://github.com/monero-project/monero/issues/6688 this might be interesting for using p2pool, that said, given all outputs are still marked to your address specifically, it might not matter
22:55:47 <DataHoarder> (Separate coinbase and non-coinbase rings)
23:22:52 <xmrvsbeast[m]> <DataHoarder> "and if XvB is reading this don't..." <- lol, would drive me nuts
23:23:46 <DataHoarder> Later on I can have more than “you got a share” but “you got a payout”
23:24:41 <xmrvsbeast[m]> is the room available on matrix?
23:25:11 <DataHoarder> Oh? I don’t know how that works, can you join it? Or how does the bridging work
23:25:53 <xmrvsbeast[m]> Is it on libera.chat server?
23:26:24 <xmrvsbeast[m]> that is bridged, but I am not seeing it
23:26:30 <DataHoarder> Yes it is here
23:26:52 <DataHoarder> #p2pool-log but unknown how they implemented the bridging or how they show channels
23:28:04 <xmrvsbeast[m]> only monero-pow shows up when searching "p2pool"
23:28:43 <xmrvsbeast[m]> might be something else that needs to be done to have it come over...?
23:28:48 <DataHoarder> Maybe you need to join it manually 
23:29:27 <DataHoarder> https://matrix.org/blog/2021/05/28/this-week-in-matrix-2021-05-28
23:30:09 <DataHoarder> > You can currently reach any channel on libera.chat by joining #<channel_name>:libera.chat. 
23:30:25 <DataHoarder> So try using /join
23:33:54 <xmrvsbeast[m]> worked, thanks!