In January 2024, we highlighted the latest release of Swanky, our suite of Rust libraries for secure computation. Since then we’ve made many changes to the codebase, both in terms of improving overall code quality and documentation, alongside new capabilities. It’s been a while since we’ve provided an update on these changes, so think of this as our biennial blog post on how things are going. And hey, maybe we’ll have even more frequent updates in the future! Swanky has existed largely as a secure computation framework for Galois projects, and as new projects have required certain secure computation capabilities over time, we’ve added them to Swanky. However, different projects have different code standards. Sometimes, we need a one-off proof-of-concept to demonstrate some capability, whereas other times we need a more robust implementation that will be used across multiple projects. This has resulted in Swanky containing a large number of capabilities that are all useful, but of various quality and usability. As we’ve further developed Swanky, and found more external interest in the repo, we’ve found the need for more stability of certain capabilities. However, we do think it is important to maintain the “testbed” nature of Swanky for future research in secure computation, and thus we deem the ability to include “less robust” code still important. With these tensions in mind, in July 2025, we split the repo into two types of crates: core and edge. For crates to be included in core, they need to achieve certain code, testing, and documentation requirements. Thus, there is an expectation that core crates will largely remain stable over time, and be easier to use by developers. Crates in edge do not necessarily have these expectations: they may be underdocumented, less robust, and may change dramatically over time. Why include these crates at all then? Because we still find them useful, and external developers have fou