Meeting summary: Seraphis Wallet Workgroup, 2 January 2023

This is a comprehensive summary, with added reference links, of the Seraphis Wallet Workgroup meeting¹ from January 2nd 2023, 1800 UTC.

Logs

The raw, unedited, full log file for this meeting:

230102-seraphis.log (73 lines)

Summary

Note: it is possible that some relevant information may be missing from this summary; read the full log file for the complete, unedited discussion.

• Participants: 7 (rbrunner7², dangerousfreedom³, woodser⁴, jberman⁵, UkoeHB⁶, Rucknium⁷, plowsof⁸)

• (1) On the state of Seraphis⁹ dev work:

• UkoeHB confirmed that he is still busy improving the Seraphis library¹⁰ but doesn’t plan any more interface refactoring: I am still chipping away at cleanup and review, making minor adjustments and bug fixes

• rbrunner7 noted that jberman has produced code using the library¹¹

• jberman explained that he implemented a basic “block scanner” using the Seraphis lib and is planning to use the library to implement a legacy full wallet scanner that makes network requests for chain data to a daemon

• jberman acknowledged that UkoeHB’s library is nice to use, usable functions are easy to find, the code is clean and structured well and confirmed that most of his time goes into Seraphis and Jamtis work

• dangerousfreedom was not able to attend, but reported just before the meeting that he started implementing the audit proofs and will probably have something to show in the next meeting

• rbrunner7 was wondering if dangerousfreedom developed some of the proofs himself; UkoeHB replied that some things require custom proofs, others can reuse existing proof structures and pointed to a relevant discussion¹²

• (2) On the Seraphis paper draft¹³:

• Rucknium was looking for some feedback on his suggestion¹⁴ to do the Seraphis paper update before asking CypherStack to create a road map; UkoeHB stated that he will continue review until it is done

• (3) On Seraphis’s cryptography:

• Rucknium was wondering who is going to fix any potential problems with part of Seraphis’s cryptography; rbrunner7 pointed to tevador and kayabanerve as likely candidates; UkoeHB replied that he can probably take care of relatively minor issues and speculated that a major issue could push them to maybe bin the whole thing

• (4) On dev recruitment efforts:

• rbrunner7 mentioned his getmonero.org dev recruitment article pull request: blog: Developer Opportunities at the Monero Project #2119¹⁵

Let me know if you find this kind of report helpful.

Feedback, edits always welcome @/about.

-3RA