Schmidt
19K posts

Schmidt
@schmidt1024
Free Speech, Privacy, Decentralization, Open Source, Fungibility

The MRL meeting reviewed the CCS proposal for I2P SAMv3 support. jpk68 answered questions, vtnerd expressed support after his code review, and the CCS proposal text was corrected. vtnerd: I'm in support after what I saw in i2p code. They could arguably improve socks to be more like tor, but there's resistance to that for reasons not clear to me rbrunner: That goes solidly above my head, but I start to worry a bit about how many things we do not do "because sybil attacks". Really no solution in sight for that? Might unblock quite some things jpk68: It is worth noting that I intend on changing/removing the last milestone of the CCS; this was suggested by vtnerd I am waiting on an email response from I2P devs about this, and will change it if they are in agreement rucknium: rbrunner, Sybil attack seems to be an unsolved problem in computer science. Big tech solves it with Captchas and personal identity info collection AFAIK. rbrunner: Ah, ok. So it's not only dragging us down at least jpk68: vtnerd, Eyedeekay responded to your comment; proposal was updated. Just letting you know :)

jberman: In communication with @cypher_stack on the audit, as noted above fleshed out more detailed Audit Goals for Phases 1a-1b I'd say the more interesting edits include: 1) the bullet on the "Unbiased key image generator", fleshing out a goal to audit both our rationale in using a new hash-to-point function in the first place, as well as the implementation / soundness of the new hash-to-point fn both koe and Cypher Stack raised questions /suggestions on that item that I think that fleshed out goal should hopefully adequately address 2) I added a bullet to verify that all detectable received outputs should essentially be able to enter the curve tree merkle tree, otherwise someone would be able to construct an output that your wallet detects as a receive that you can't spend (see the section "Converting outputs to tuples in prep for insertion to the curve tree merkle tree") jeffro256: 3) I added more concrete bullets on auditing the Rust FFI 4) As per Cypher Stack suggestion, I moved hash_grow and point_to_cycle_scalar to "Audit 2: Curve Tree Building", since those items more directly correspond to building the tree 5) I included a catch-all statement that the goal of the audit is to answer the question "Is the linked PR fit for use in Monero?" and that any insights that would help answer that question are appreciated, even if not explicitly mentioned in the "Audit Goals" for each PR Above are main highlights of the changes Rucknium: Thanks, jberman for all your work on the audit scoping and thanks to Cypherstack and irc_ukoehb for initial review of the scope.

FCMP beta stressnet. github.com/seraphis-migra… x.com/MoneroResearch…














FCMP code integration audit overview. github.com/seraphis-migra… x.com/MoneroResearch…


*hates being isolated* *starts socializing* *immediately wants to go home*


