UkoeHB

> Since the view keys are derived from the spend key, publishing a large number of spend keys would essentially transform the currently opaque blockchain into a transparent one, leaking...

> The hashes bind the X and U components, which in turn binds the resulting key image, preventing double spending. If the DLP between `X` and `U` is known, then...

Here is my general take on this proposal. Seraphis is a transaction protocol loaded to the brim with complex changes compared to RingCT. All of those changes are concise and...

> I actually believe the modified switch commitment scheme, which would be a wallet protocol change with minimal performance costs and trivial implementation, should be done with Seraphis. While any...

> It has no effect on the validation of Seraphis. The changes in this proposal would only be needed at consensus - you are effectively embedding a transaction protocol under...

> Nobody is asking you personally to review or implement the protocol. Well... multisig would require quite a bit of work to make it compatible with the changes to `Ko`,...

`[10-12-2022 16:59:49] meeting time https://github.com/monero-project/meta/issues/740` `[10-12-2022 16:59:49] 1. greetings` `[10-12-2022 16:59:49] hello` `[10-12-2022 17:00:13] hi` `[10-12-2022 17:00:18] Hello` `[10-12-2022 17:01:01] Hi` `[10-12-2022 17:01:01] Hello.` `[10-12-2022 17:01:44] Hi` `[10-12-2022 17:02:56] 2....

> The purpose of the feature is precisely to avoid the user having to think about which specific implementation will be used, in the most general case. The three variants...

> No translation is necessary because the names of the parameters are irrelevant for the caller (unless they coincide with their labels) and the labels of the parameters are irrelevant...

> Yes, a thorough code review will have you make sure all implementations are correct with respect to their specification. That is true of any system. If they don't, then...