Hi Vincent, This is exactly what I was hoping to see — thanks a lot for sharing the crypto branch.
I’ve been following the SEP discussion specifically to contribute around the key exchange work, so knowing that this part is nearly ready is perfect timing for me. I’ll go through the branch today and start with a focused contribution (docs/tests or a small cleanup where it helps the PR readiness), and open a PR against the crypto branch soon. Really glad to sync at this stage — looking forward to contributing here. Best regards, Vishwas On Thu, 8 Jan, 2026, 8:12 am Vincent Macri, <[email protected]> wrote: > Thank you for your interest Vishwas! > > Brian, Taha, and I are working on implementing the SEP in the crypto > branch of my Sage fork: https://github.com/vincentmacri/sage/tree/crypto > > Key exchange is nearly ready for a first PR, I just need to find the time > to do a documentation and code cleanup pass. > > You're welcome to open a PR against my crypto branch as well (although I > can't do anything about GitHub account restrictions). > On 2026-01-06 12:08 a.m., Vishwas Bajaj wrote: > > [△EXTERNAL] > > Hi all, > > I’ve been following the recent SEP discussion on improving Sage’s public > key cryptography framework, particularly the plan to start with key > exchange and build a common, math-oriented API. > > As a small concrete step aligned with that discussion, I’ve pushed a > minimal branch to my fork that adds only documentation and test > scaffolding (no cryptographic logic and no API changes). The intention is > to document design intent and provide a place for future TestSuite-based > correctness checks (e.g. shared-secret agreement for key exchange > protocols). > > Branch link: > https://github.com/v02709928-png/sage/tree/pk-crypto-test-scaffold > > I attempted to open a pull request, but PR creation appears to be > restricted for my account at the moment, so I wanted to share the branch > here instead in case it is useful for discussion or future reference. > > Best regards, > Vishwas -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion visit > https://groups.google.com/d/msgid/sage-devel/4f2c5c7d-26f4-4ef5-90fe-02706b079914n%40googlegroups.com > <https://groups.google.com/d/msgid/sage-devel/4f2c5c7d-26f4-4ef5-90fe-02706b079914n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion visit > https://groups.google.com/d/msgid/sage-devel/e42bf849-ab4d-4c65-a52e-cda69cd4289d%40ucalgary.ca > <https://groups.google.com/d/msgid/sage-devel/e42bf849-ab4d-4c65-a52e-cda69cd4289d%40ucalgary.ca?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/sage-devel/CAO9x8E5sBmfCz4Up9wTVAceaG_G-y6uLM0Noau5aj-uYWWpEgQ%40mail.gmail.com.
