14:02:35 <m-relay> <alex:agoradesk.com> https://github.com/monero-project/monero/pull/9050 14:02:35 <m-relay> <alex:agoradesk.com> luigi1111 please review/merge this PR as soon as possible. The multisig wallet storage leak is debilitating. 14:03:20 <luigi1111w> is there one for release too? 14:03:30 <luigi1111w> will wait 24 hours from submission at least 14:04:30 <m-relay> <alex:agoradesk.com> jeffro256: could you make one for RELEASE, please? 14:12:15 <selsta> was just about to ask the same, this seems relevant for release 14:17:23 <m-relay> <r4v3r23:monero.social> https://github.com/monero-project/monero/pull/9049 14:18:05 <m-relay> <r4v3r23:monero.social> can some one review this, minor change to fix unsigned tx payload not adding change output key images (as its supposed to) 14:18:09 <m-relay> <r4v3r23:monero.social> ive tested it and it works 15:35:12 <GrapeJuice9000> hello 15:35:24 <GrapeJuice9000> I read this article about Monero, https://www.wired.com/story/monero-privacy/ 15:35:33 <GrapeJuice9000> Just hoping those flaws have been fixed 15:35:42 <m-relay> <ofrnxmr:monero.social> Monero 15:36:03 <m-relay> <ofrnxmr:monero.social> #monero 16:06:46 <sech1> This was all fixed way back in 2017, why they keep bringing it up, lol 16:52:39 <rbrunner> Well, other coins are still running on their 2017 tech. Just saying, you can be forgiven to not know how aggressively Monero marches forward 16:54:48 <m-relay> <jeffro256:monero.social> yes 23:29:19 <m-relay> <trasherdk:monero.social> litmus test for all matrix users who see the above image and continue using reply 23:32:14 <selsta> .merges 23:32:14 <xmr-pr> Merge queue empty 23:40:26 <selsta> .merge+ 9050 9051 9028 9029 9030 9033 9034 9035 9036 9038 9039 9044 9045 9046 9047 23:40:27 <xmr-pr> Added 23:40:44 <m-relay> <jeffro256:monero.social> Poor merge queue never gets a break 23:41:35 <selsta> jeffro256: can you re-review 9042 / 9043? it was updated after your comment 23:41:51 <m-relay> <jeffro256:monero.social> Ofc