08:42:41 <m2049r> Inge-: not that i've seen. if it's not a node issue, what happens if you restore from seed?
09:15:39 <Inge-> m2049r: I will try from seed. if I flip to a different wallet, it synchs as expected - so only this single wallet has the issue. I'll let you know how restore from seed goes
10:22:21 <hyc> my hashes, seem to match https://paste.debian.net/1164154/
14:24:21 <selsta> I forwarded the binaries to bF, not sure if he has time to release them today
15:38:23 <Inge-> m2049r: quick update. recreate from seed scanned no problem. old wallet hangs on scanning, no progress but phone getting warm = doing *something*
15:39:05 <moneromooo> If you set logs to 2, do you get warnings about a bad hashchain ? It's supposed to recover but might not.
15:41:37 <Inge-> This is Monerujo (yeah I know, kind of off-topic)
15:43:26 <moneromooo> It doesn't use wallet2 ?
15:43:47 <selsta> it does
15:45:19 <Inge-> but maybe no easy way to set logs to 2 from the ui
15:47:49 <moneromooo> MONERO_LOGS=whatever (if it doesn't override it)
15:47:52 <moneromooo> (env var)
15:49:34 <Inge-> I'm guessing this would require a root or emulated android?
15:49:52 <dsc_> Compile something :)
15:50:30 <Inge-> Considering it. kind of strange for it to be stuck scanning like that
16:07:21 <m2049r> Inge-: i can get you a version which has logs on if you like
16:21:11 <selsta> https://paste.debian.net/hidden/0e04671f/
16:21:18 <selsta> anything major I forgot in release notes?
16:23:55 <moneromooo> serializt
16:24:02 <moneromooo> serialization format changes
16:24:11 <moneromooo> To remove most boost usage
16:24:31 <moneromooo> rpc: always send raw txes through P2P (don't use bootstrap daemon)
16:24:53 <moneromooo> (this mitigates stranger's nodes from being jerks)
16:32:10 <ErCiccione> selsta: i would add that the software is necessary to be part of the network upgrade and bla bla bla. Just to make sure people understand they have to use it
16:33:15 <ErCiccione> also `monero-android-armv8-v0.16.0.50.tar.bz2`
16:33:35 <ErCiccione> ^ the hash
16:34:42 <selsta> ErCiccione: yea I used the wrong template
16:39:49 <selsta> updated, added suggestions: https://paste.debian.net/hidden/341af3fa/
16:40:00 <selsta> ErCiccione: do you have time for the blog post?
16:40:19 <ErCiccione> yeah
16:40:22 <selsta> ty
16:51:51 <dsc_> win 3
17:03:28 <ErCiccione> selsta: https://github.com/monero-project/monero-site/pull/1199
17:03:51 <ErCiccione> i added some stuff, the logo and made a minor correction (network update -> network upgrade)
17:06:34 <sarang> Those hashes were verified?
17:06:43 <sarang> And the links?
17:11:35 <ErCiccione> We can test that everything is working as usual as soon as binaryfate PRs the hashes
17:11:57 <ErCiccione> the post is up but we are not going to merge it now. The usual checks are needed
18:12:32 <Inge-> m2049r: sure if you think it is worthwhile to look into!
18:13:38 <vtnerd> m2049r : the problem is (kind-of) on the wallet side then, and not d++/pool in daemon. Restricted rpc calls never return txes in the "stempool" to prevent data leakage
18:15:06 <vtnerd> you could have tracking per TCP connection on the daemon to return this, not sure how much work this would be - and it wouldn't work if the wallet rotated connections (unless there was client auth)
20:49:31 <binaryFate> <ErCiccione> We can test that everything is working as usual as soon as binaryfate PRs the hashes <-- I'll do my best to do tomorrow (Friday)
21:40:16 <selsta> I still like the idea of increasing outgoing connections default, what kind of numbers did you think of moneromooo? 8 -> 12?
21:40:48 <moneromooo> I was thinking of 10. Nothing drastic. It might have non obvious side effects.