00:36:12 <nikg83[m]> With seraphis update can monero have ability to work with layer2 solution ?
00:46:44 <UkoeHB> nikg83[m]: not that I know if
00:46:45 <UkoeHB> of
00:49:03 <UkoeHB> there is paymo https://eprint.iacr.org/2020/1441.pdf but it uses PoW-based timelocks
00:53:39 <nikg83[m]> UkoeHB: Is this being looked into or it’s just a paper for now ? 
00:56:31 <UkoeHB> nikg83[m]: it's just a paper that has been around a while
00:59:31 <nikg83[m]> UkoeHB: I don’t understand much of that paper, does it need change in monero code (some requirement) ? Which can be done during seraphis update ? 
00:59:31 <nikg83[m]> I guess we need this paper reviewed once seraphis audits are done 
01:22:29 <UkoeHB> No idea
02:47:17 <Rucknium[m]> nikg83: There are at least three papers proposing Monero payment channels. No implementations yet. Payment channels acting as networked 2nd layers have privacy problems that have no known solutions. I'm personally not optimistic on them.
09:00:11 -xmr-pr- j-berman opened issue #8670: Wallet can miss processing spend txs in the pool
09:00:11 -xmr-pr- > https://github.com/monero-project/monero/issues/8670
09:15:31 <jozsef[m]> "low tx rates, high tx fees, and long confirmation times" - really?
09:17:57 <moneromoooo> These are all subjective, so not useful. You can check recent tx rate and tx fees with bc_dyn_stats 1000. Confirmation times are typically around 2 minutes.
09:18:59 <moneromoooo> (for tx fees, you've got to multiplty the base fee by ~1300 or so, the size of a typical tx)
09:23:44 <sech1> ~1530
12:15:11 -xmr-pr- Gingeropolous opened pull request #8671: update readme with v0.18.1.2 version number
12:15:11 -xmr-pr- > https://github.com/monero-project/monero/pull/8671
15:27:17 <hyc> looks shady, possible backdoor
15:27:21 <hyc>  /s