12:00:54 <selsta> .merges
12:00:54 -xmr-pr- 7084 8052 8145 8161 8163
12:18:47 * leonarth morning!
14:22:44 <selsta> jberman[m]: should we merge view tags after bp+ or does it not matter?
14:25:25 <jberman[m]> thinking it would probably be easier if I handle the merge conflicts, so bp+ would go first in that case
14:44:15 <jberman[m]> dynamic fee PR too
14:45:18 -xmr-pr- undeath opened issue #8189: monerod excessive hard drive writes
14:45:18 -xmr-pr- > https://github.com/monero-project/monero/issues/8189
14:45:44 <jberman[m]> I guess it doesn't really matter think there are gonna be conflicts across all 3
14:48:40 <selsta> soo many conflicts with the multisig changes too
14:51:14 <jberman[m]> here's what I can do: when the time comes, I could just fork from moneromoo's + ukoehb's repos, and submit PR's that resolve conflicts to their repos haha. less annoying work for them, I'm fine with it
14:52:43 <jberman[m]> order doesn't really matter in that case
15:02:20 <selsta> I guess we can do that in the worst case if one of the patch authors is unavailable
15:02:39 <selsta> otherwise it's not necessary yet, we still have to get BP+ approved :D
15:07:36 <jberman[m]> merging dynamic fee + view tags would allow others to start updating code to handle them. so I think just merging as soon as they seem ready is best strategy
15:11:51 <moneromooo> BP+ is not approved ?
15:12:09 <moneromooo> I thought it'd been ready for like a year.
15:13:36 <moneromooo> Nothing left to do AFAICT, looking at the patch on github.
15:13:56 <jberman[m]>  vtnerd  is still working through final review (and I keep piling shit on his plate in monero-lws -- sorry vtnerd :/ )
15:14:39 <moneromooo> Ah. Well, given I barely remember the code now, it's going to be another "introduce bugs on review" case, isn't it. Oh well.
15:17:44 <jberman[m]> sounds worth it to get another audit on this implementation done
15:51:48 <jberman[m]> i guess not if this is the exact code that was audited
19:21:27 <r4v3r23[m]> are the major improvements to multsig that DNMs have been requesting coming this hard fork or with seraphis?
19:25:41 <moneromooo> There are multisig improvements ready on github. Whether they're the ones you want, I dunno. Look at the patch, the message probably has an overview.
19:35:21 <jeffro256[m]> Does Seraphis use BP range proofs ?
19:35:36 <r4v3r23[m]> looks like ppl who tested it say it works. looks like this is the "big fix" then
19:35:46 <r4v3r23[m]> s/looks/guess/, s/like//
19:41:11 <UkoeHB> jeffro256[m]: I am using the bp+ code that is currently PRd for next hardfork
19:42:19 <jeffro256[m]> UkoeHB cool, thanks!
19:57:36 <monerobull[m]> who made docker-monero-node?
20:13:41 <monerobull[m]> i just want to install the node on my sdd. why does it have to be such a pain
20:51:46 <monerobull[m]> Seth For Privacy: i have no idea why but i gave up and started copy-pasting the commands from your monerod guide
20:52:04 <monerobull[m]> and it magically started syncing onto my ssd
20:53:40 <sethforprivacy> Not really a topic for this channel, but just use: https://sethforprivacy.com/guides/run-a-monero-node/
20:53:48 <sethforprivacy> It uses my own Dockerized monerod image