05:25:24 new protocol w/ deniablity: http://4o7umzlwx7unb64vgnqj4yhwtlqmlnyx3gawayfni623hqqw5buy5pid.onion/vault1317-signal-dakez 06:39:46 I wonder why dakez chose x25519 and not Ristretto 09:26:05 May be of interest -> https://github.com/MerosCrypto/asmr/tree/monero 09:33:23 Author here :) Was waiting to post this directly in Monero communities until that branch was merged. That said, I did post in #m-d when I started said branch as I was looking for someone who may be interested in looking it over. 09:34:19 The underlying protocol still isn't... signed off on, and I believer sarang was heading that research up. Even if it is, this is its own PoC without any audit. 09:36:25 That said, it does fully handle pathing (success/failure), have coin selection at runtime (not going to have each project supply their own build command), and some tests :) The Monero files specifically need more work done before they also meet that feature set though. 09:39:44 I'm not heading up research on the project you linked 09:41:07 Sorry, didn't mean to suggest you were the paper's author. I thought you were reviewing it further, but I guess I was wrong. My bad. 09:42:01 I do know who h3sh4d is and have actually reached out to him 09:58:12 I took a look at it, but this should not be construed as any kind of formal review 10:00:02 Thanks for the clarification :) 12:29:10 kayabaNerve: Would you mind making a post on r/monero as well once ready? 12:29:21 once you feel it is sufficiently ready* 18:01:41 dEBRUYNE: When it's ready.