00:24:40 What would it take for multisig to be no longer marked as "experimental"? 00:24:57 It'd be nice to be able to add it to the GUI 00:26:04 https://github.com/monero-project/monero-gui/pull/3990#issuecomment-1204406087 00:55:35 wallet2 is not an environment where that can happen IMO. Preferably a third-party has the resources to do it thoroughly and can present a GUI for it. 00:56:26 Why not? There are facilities provided for it which can easily be used in QML over the bridge (libwalletqt) 00:57:34 Because wallet2 is a spaghetti mess and multisig is potentially adversarial tx construction. 00:58:20 Also multisig uses bespoke protocols with no papers and insufficient auditing. 00:59:04 Would it still be acceptable to add it to the GUI if it's only available in "Advanced" mode, and features warnings of it being experimental? 00:59:15 It would be a shame if not :( 00:59:46 That's up to selsta but I'd encourage no since it's currently in maintenance mode. 01:00:27 And adding to the GUI would increase the maintenance surface for a very low-use feature. 01:01:46 I think usage of it (as well as its sort of value prospect, due to ease-of-use) could be increased using GUI support, both for 'traditional' and QR code-enabled workflows 01:02:08 I wouldn't know much about the safety of the implementation though, so thanks for your advice :) 01:02:42 Maybe there can be a flashing red light that says "WARNING" in big letters 01:04:55 How many devs have been lost on the shoals of multisig 01:05:39 I have been working on a PoC, and it mostly works already 01:14:19 I did a local 2/2 transaction on stagenet and it seemed to work fine 01:24:10 jpk68: https://github.com/freigeist-m/monero-multisig-gui/tree/master/ 01:25:24 Yes, I am using that as a sort of reference 10:20:28 I'm against merging any multisig into GUI before it's marked not experimental. 15:15:01 Good to know. I guess I'm just curious where the distinction is drawn 15:15:23 For example, still having it in the CLI, but not in the GUI, even if it has to be explicitly enabled or something 15:27:38 Well, the "addressed public" is different, IMHO, CLI -> more experienced users, GUI -> users that are often less so. I would trust the average CLI user more to be able to judge whether they want to use that, than I would trust the average GUI user. 15:28:01 Or, in other words, even with warnings, having multsig in the GUI is in danger of sending the wrong signal 15:29:17 ^ it will signal that it’s ready to use and will be supported 15:29:17 And whether "experimental" or not, our current multisig technology with its exponentially larger data exchanges with growing numbers of M and N somehow does not really cut it 15:29:40 Kind of sucks, but yeah, I feel like you're right 15:29:59 It does certainly such :) 15:30:02 *suck 15:30:57 Maybe the PR can still be published as a draft, and those who would find it useful can compile from source. 15:31:14 The work is already done, haha. It took way less time than I had expected 15:31:24 Some here may find it interesting :) 15:31:32 Why not, would be interesting how you approached the whole thing. 17:32:09 Can someone explain why this is needed and if it needs to be done for every additional block as well? https://github.com/seraphis-migration/monero/blob/b7b4e5790a52a24f3d5cd0aca8b2b2ec50cfe855/tests/core_tests/fcmp_pp.cpp#L446-L458 17:32:21 I'm trying to add tests for the relative lock. 21:08:23 @rbrunner7:monero.social Done. 21:08:24 https://github.com/monero-project/monero-gui/pull/4696 21:15:41 Tested by receiving and then sending a transaction to CypherFaucet on stagenet, using a 2/2 setup.