Confidential coordination infrastructure for multiparty systems
Today, Enclave becomes The Interfold. The name Enclave suggested containment, a sealed boundary around sensitive computation. It carried a strong association with hardware security systems such as TEEs and HSMs. But what we built is coordination infrastructure that distributes execution itself: allowing independent parties to produce shared, verifiable outcomes from
February marks a major transition point for the protocol: from deep cryptographic R&D toward full system integration and testnet validation. The primitives are in place. The focus now is integration, coordination, and operational readiness. As part of this shift, we’re opening the conversation to the broader ecosystem.
Happy New Year, privacy builders & systems alchemists! For those new here: Enclave is an open-source protocol for collaborative confidential compute, enabling shared computation with verifiable outcomes, without exposing underlying data. We’re kicking off the year by preparing for a public testnet, pushing forward our secret ballot protocol and
This article is the first entry in our new Enclave Cryptography series: technical deep dives into the cryptographic components that make Collaborative Confidential Compute possible in Enclave
Aragon and Enclave are working to introduce verifiable secret ballots built on Enclave’s encrypted execution network and reference protocol CRISP. Once live, DAOs and other onchain entities can enable verifiable secret ballots and private voting through Aragon OSx, with minimal setup and no reliance on trusted coordinators. Read Aragon&
