00:21:04 Does anyone know if something like Elligator can work with CSIDH? I am having a hard time finding information on this 00:27:15 not sure if you like clankers 00:27:15 try grok deep research and ask for sources + the info 00:27:15 has been a good tool for me when i cant find info 03:43:28 @jpk68:matrix.org: I'm aware of an I(E/R?)TF discussion on indistinguishable encodings for Kyber, which isn't what you're asking for but I want to throw out there. 03:56:01 It seems the CSIDH public key is just a field element over a prime p from the setup? That seems promising for effecting an indistinguishable mapping. 04:12:16 I wonder if the methodology of Elligator proper could simply be applied here 05:12:51 I'm pretty sure no invertible indistinguishability mapping is known for CSIDH. One hint that this is the cases is that there is no known way to "hash to a supersigular curve" with unknown endomorphism ring. https://eprint.iacr.org/2022/518 13:42:29 A new paper on selfish mining, Monero not mentioned: https://eprint.iacr.org/2026/1629 13:55:36 @sgp_: The title in itself is very depressing 14:53:41 the next time someone on Reddit complains "view keys will kill monero" just sent them this silly paper https://eprint.iacr.org/2026/872 14:55:01 GM 14:55:01 I have a question.… 14:55:01 Would a small test only PR for CARROT /get_transactions split output be useful? On fcmp++-stage, it would extend the existing functional transfer.py test to verify that a confirmed CARROT v2 transaction returned with split=true, prune=false has non-empty pruned_as_hex and prunable_as_hex, and that concatenating them exa[... more lines follow, see https://mrelay.p2pool.observer/e/3szE1p8LcGI1Qzla ] 16:14:52 @boog900:monero.social or @jberman:monero.social : Do you know the answers to my questions about tx relay logs? > <@rucknium> I'm trying to understand tx relay logs under tx-relay v1 and v2. 16:22:11 You dinask me but… 16:22:11 from what I understand, yeah, that looks right… with v1 the logs look the same for stem and fluff because that difference isn’t printed there, with v2, fluff announces the hashes first and requests the full tx only if needed, while stem still uses “NOTIFY_NEW_TRANSACTIONS” like v1. 16:22:11 The only caveat is that “No requests for tx” doesn’t always mean “I already have it”, just that there was no pending request for it. 16:25:15 I would have to check for the exact log lines but that looks correct 16:30:41 @rucknium: yep that's all correct 16:33:23 Thanks everyone :) 22:34:19 https://blog.casa.io/how-built-reliable-ai-pentest/