new protocol w/ deniablity: 4o7umzlwx7unb64vgnqj4yhwtlqmlnyx3ga…uy5pid.onion/vault1317-signal-dakez

I wonder why dakez chose x25519 and not Ristretto

May be of interest -> github.com/MerosCrypto/asmr/tree/monero

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.

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.

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.

I'm not heading up research on the project you linked

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.

I do know who h3sh4d is and have actually reached out to him

I took a look at it, but this should not be construed as any kind of formal review

Thanks for the clarification :)

kayabaNerve: Would you mind making a post on r/monero as well once ready?

once you feel it is sufficiently ready*

dEBRUYNE: When it's ready.