06:09:53 To clarify the scope: 06:09:53 monero-serai assumes persistent wallet state for key image and commitment 06:09:53 mask derivation. That works for nodes/servers, but not for browsers. 06:09:53 [... more lines follow, see https://mrelay.p2pool.observer/e/--z53OIKNWphZHBY ] 15:06:33 @onyx_prot:matrix.org: I'm unsure what you mean about assuming 'persistent wallet state'. Key images also cannot be derived from view keys only, and shares of a view key _inside the hash function_ wouldn't be homomorphic. It increasingly sounds like you're deferring to an LLM which is misleading you. 15:06:41 If you want to share your work though, please do so. 15:17:34 @kayabanerve:matrix.org: You're right, I compressed too much. Let me clarify: 15:17:34 Key images: KI = x * Hp(P) — uses spend_key shares, FROST aggregates 15:17:34 partial KIs. Server holds 1 share, threshold is 2, can't compute alone. 15:17:34 Commitment masks: view_key ECDH, computed client-side:[... more lines follow, see https://mrelay.p2pool.observer/e/v9TN7OIKWGI1d2Rp ] 15:18:34 1) That even more sounds like an LLM output. 15:18:34 2) monero-oxide doesn't use `.keys`. 15:20:14 So not to say your work doesn't contribute, to say if your reasoning against monero-oxide is the usage of `.keys`, you're misinformed on that topic. 15:23:50 Though again, if you have a contribution, please, share it. Solely talking about as an idea obviously causes a lack of proper context 15:23:59 Fair. Here's actual code, not LLM summary: 15:23:59 1. Lagrange coefficients for 2-of-3 (frost_dkg.rs): 15:23:59 pub fn compute_lagrange_coefficients(signer1: FrostRole, signer2: FrostRole) -> (String, String) {[... more lines follow, see https://mrelay.p2pool.observer/e/s-Tm7OIKYVc1aV9U ] 15:24:19 Ban? 15:25:24 monero-oxide's monero-wallet does not require any daemon. 15:25:38 Not to say it meets your needs, to clarify that comparison still seems inaccurate. 15:26:41 None of those code snippets are remarkable, being a straightforward lagrange interpolation and simple commitment mask derivation. I'd recommend linking a GH repo, or yes, not bothering to continue talking about the code you won't actually publish for discussion here. 15:26:53 Though I wouldn't outright call for a ban 😅 15:27:09 But in general, since this seems like an LLM, I'd say yes, it's probably a waste of time. 15:29:49 hhhh You're right. Crypto is standard, nothing new there. 15:29:49 The work is a shipped escrow product — browser UI, API, dispute 15:29:49 resolution. That's it. 15:29:49 [... more lines follow, see https://mrelay.p2pool.observer/e/jqz87OIKSURfSnA3 ] 15:31:19 bro 15:34:00 K, now I'm call for ban lol 15:34:09 @tobtoht:monero.social: was right 16:06:59 Fkn skull / facepalm 16:07:14 Even the linebreaks are pasted from the bot 16:55:10 banned 18:03:11 YES YES YES YES YES.* 18:03:13 I LOVE THE HAMMER 22:40:49 @kayabanerve:matrix.org: Can you attend the MRL meeting tomorrow? Two agenda items relevant for you: zkSecurity quote for reviewing Elliptic Curve Divisors for FCMP++ and Goodell (2026) "Generalized Bulletproofs for Opening Vector Commitments." (https://github.com/cypherstack/generalized-bulletproofs-fix)