- 
r4v3r23[m]<nahnahnah722828[> "The date for the next hard..." <- dev meeting to formalize the next hardfork (not seraphis)
- 
gingeropolousman, my monerod got stuck on Height: 2585257/2585257
- 
gingeropolous858 in cnxns. wtf
- 
gingeropolousand ~230 ips in my blocked list from my script thing
- 
ErCiccioneMaybe i'm misunderstanding the issue, but the daemon should switch to fast sync after it completed the first sync of the blockchain no? asking because that resources usage is insane: monero-project/monero #8189
- 
moneromoooIt should.
- 
hycit's the opposite - it uses fast sync for IBD, and safe sync after that
- 
hycon the assumption that once caught up, the number of incoming writes is small
- 
r4v3r23[m]<rbrunner> "github.com/monero-..." <- thanks for the PR list, glad to see the HF start to shape up
- 
r4v3r23[m]i saw a couple of PRs get merged to v17 branch that change the way unconfirmed balances are displayed
- 
r4v3r23[m]a hard fork sounds like a good time to introduce this change in wallet UX
- 
hycshouldn't the v0.17 branch be dead now, since we're preparing v0.18?
- 
selstadepending on when we release 0.18 there might still be a 0.17 release
- 
selstain case a bug shows up or whatever
- 
hycsounds like wasted effort at this point. isn't v0.18 due soon, like within a month?
- 
selstawe will talk about it in the next dev meeting
- 
r4v3r23[m]<hyc> "shouldn't the v0.17 branch be..." <- monero-project/monero #8154
- 
r4v3r23[m]> <@hyc:libera.chat> shouldn't the v0.17 branch be dead now, since we're preparing v0.18?
- 
r4v3r23[m]
- 
r4v3r23[m]
- 
r4v3r23[m]cant really tell whats going on here - the PR was merged into master last year but also just merged into `release-v0.17`
- 
selstabecause they needed to changes for haveno IIRC