03:37:58 Key images alone aren't enough to mess with anything, right? 03:38:11 Can't burn outputs because you still wouldn't form a valid ring signature? 03:38:50 The minimum amount of data required to burn an output which isn't yours is still the private key, even if you have every single other piece of info? 03:57:04 Eh. Sort of an idiot for asking. There's multiple existences of standing commentary this. I got nervous and asked as most key image discussion relates to spent outputs (though I do understand the mempool causes a pseudostate as well requiring the private key still be required). Sorry for being a bother 04:09:03 yes correct 04:09:35 you cannot construct a valid transaction with someone else's key image 06:36:49 Is there a way to prove the accuracy of a published key image which has yet to be spent? I assume its standing proof can be minimized to not be of ring form and that also wouldn't be enough to cause any havoc? 06:37:16 But I'd also assume there's no standing impl of such work :/ Can't seem to find any 06:41:20 Oh. I'm a further idiot. The standing wallet does exactly this. I was poking around for single ring constructions and saw that. I assumed it wouldn't assume a malicious/invalid counterparty. My bad again, sorry. 07:10:59 The Windows build of Master failed. I'm looking into it. Should be easy to fix. 07:14:01 it's already fixed 07:31:39 Ah. Thanks. 11:38:24 .merge+ 8013 8014 11:38:24 Added 14:52:02 vtnerd do you or anyone else recall the default dandelion++ stem length? 14:55:11 20% fluff probability, or what do you mean exactly? 14:55:46 src/cryptonote_config.h has DANDELION defines 14:59:09 perfect selsta, thanks 15:48:07 UkoeHB: I just left the review on #7877, very good work! I concentrate on src/multisig/ impl (not that much on the wallet side, but I can do it later this week) 15:58:45 thank you! 16:00:45 <3