The Interfold

Note: The Interfold was previously known as Interfold.
Many repositories, packages, and CLI tools still use the interfold name while the project transitions.

This is the monorepo for The Interfold, an open-source protocol for confidential coordination.

The Interfold leverages a combination of Fully Homomorphic Encryption (FHE), Zero-Knowledge Proofs (ZKPs), and Multi-Party Computation (MPC) to enable Encrypted Execution Environments (E3), with integrity and privacy guarantees rooted in cryptography and economics, rather than hardware and attestations.

Documentation

Full documentation is available at: https://docs.theinterfold.com

Quick Start

Follow instructions in the quick start section of the documentation.

See the CRISP example for a fully functioning example application.

Getting Help

Join the community Telegram group.

Contributing

See CONTRIBUTING.md.

Development

This section covers the essential commands for setting up and working with the Interfold codebase locally.

# Install dependencies
pnpm i

# Build the project
pnpm build

# Clean build artifacts
pnpm clean

Testing

⚠️ Important: Always run tests through pnpm scripts, not directly via cargo test or other build tools. The pnpm scripts ensure necessary setup steps are executed (e.g., building required binaries, setting up test environments) that may be skipped when running tests directly.

Test Scripts

The monorepo provides several test scripts for different components:

• pnpm test - Runs all tests across the entire monorepo:

  • EVM/Smart contract tests (evm:test)
  • Rust crate tests (rust:test)
  • SDK tests (sdk:test)
  • Noir circuit tests (noir:test)

• pnpm rust:test - Runs all Rust crate tests in the crates/ directory. This script runs tests for all crates in the workspace, not just ciphernode-related crates.

• pnpm evm:test - Runs tests for the EVM smart contracts in packages/interfold-contracts.

• pnpm sdk:test - Runs tests for the TypeScript SDK in packages/interfold-sdk.

• pnpm noir:test - Runs tests for Noir circuits in the circuits/ directory using nargo test. Requires the Noir toolchain (nargo) and Barretenberg (bb) to be installed and on your PATH.

• pnpm test:integration - Runs integration tests from tests/integration/. These tests may require prebuilt binaries and can be run with --no-prebuild if binaries are already available. Pre-built circuit artifacts for the configured BFV preset must be present in the circuits/ artifacts directory.

Running Individual Test Suites

# Run only Rust crate tests
pnpm rust:test

# Run only EVM/smart contract tests
pnpm evm:test

# Run only SDK tests
pnpm sdk:test

# Run only Noir circuit tests
pnpm noir:test

# Run only integration tests
pnpm test:integration

# Run integration tests without prebuild step (if binaries already exist)
pnpm test:integration --no-prebuild

Contributors

гλ	Hamza Khalid	ctrlc03	Auryn Macmillan	Cedoor	Giacomo
samepant	Cristóvão	Nathan Ginnever	Malingshu	marv	Bryant
Zara	Armanc	SUBHASISH BEHERA	Jan-Felix	callumweb3	cryptam

Minimum Rust version

This workspace's minimum supported rustc version is 1.91.1.

Architecture

The Interfold employs a modular architecture involving numerous actors and participants. The sequence diagram below offers a high-level overview of the protocol, but necessarily omits most detail.

sequenceDiagram
    participant Users
    participant Interfold
    participant CiphernodeRegistry
    participant RandomnessProvider
    participant E3Program
    participant ComputeProvider
    participant DecryptionVerifier

    Users->>Interfold: request(parameters)
    Interfold->>E3Program: validate(e3ProgramParams)
    Interfold->>ComputeProvider: validate(computeProviderParams)
    ComputeProvider-->>Interfold: decryptionVerifier
    Interfold->>CiphernodeRegistry: requestCommittee(e3Id, legacySeed, threshold)
    CiphernodeRegistry->>RandomnessProvider: requestRandomness(e3Id)
    RandomnessProvider-->>CiphernodeRegistry: requestId
    CiphernodeRegistry-->>Interfold: success
    Interfold-->>Users: e3Id, E3 struct

    Note over RandomnessProvider: Chainlink verifies and stores the VRF response
    CiphernodeRegistry->>RandomnessProvider: getRandomness(requestId)
    RandomnessProvider-->>CiphernodeRegistry: random word and fulfillment context

    Users->>Interfold: activate(e3Id)
    Interfold->>CiphernodeRegistry: committeePublicKey(e3Id)
    CiphernodeRegistry-->>Interfold: publicKey
    Interfold->>Interfold: Set expiration and committeePublicKey
    Interfold-->>Users: success

    Users->>Interfold: publishInput(e3Id, data)
    Interfold->>E3Program: validateInput(msg.sender, data)
    E3Program-->>Interfold: input, success
    Interfold->>Interfold: Store input
    Interfold-->>Users: success

    Users->>Interfold: publishCiphertextOutput(e3Id, data)
    Interfold->>DecryptionVerifier: verify(e3Id, data)
    DecryptionVerifier-->>Interfold: output, success
    Interfold->>Interfold: Store ciphertextOutput
    Interfold-->>Users: success

    Users->>Interfold: publishPlaintextOutput(e3Id, data)
    Interfold->>E3Program: verify(e3Id, data)
    E3Program-->>Interfold: output, success
    Interfold->>Interfold: Store plaintextOutput
    Interfold-->>Users: success

Loading

🚀 Release Process

Quick Release

# On a release branch: update versions, commit, and push the branch.
pnpm bump:versions 1.0.0

# Open a pull request. Wait for CI, then merge it.

# On an updated and clean main branch: create the release tag.
git checkout main
git pull --ff-only
pnpm release:tag 1.0.0

bump:versions never creates a release tag. release:tag accepts only the exact origin/main commit and starts the release workflow.

Release Order

1. Create a release branch from current main.
2. Run pnpm bump:versions X.Y.Z.
3. Open a pull request and wait for all required CI jobs.
4. Merge the release pull request.
5. Update local main with git pull --ff-only.
6. Run pnpm release:tag X.Y.Z.
7. Wait for the Release workflow.

For a pre-release, use a semantic pre-release version:

pnpm bump:versions 1.0.0-beta.1
pnpm release:tag 1.0.0-beta.1

What the Release Workflow Requires

The tag workflow does not repeat the repository CI that qualified the merged main commit. Publication cannot start until these release checks succeed:

• The tag points to a commit in origin/main.
• Linux and Apple Silicon binaries build.
• The circuit-artifacts branch contains the complete source-matched release matrix.

After qualification, the workflow publishes versioned container images and npm packages. A stable release also builds the DAppNode package. It then promotes the latest container aliases and the stable Git tag. The GitHub release is the final step. Rust workspace crates are not published to crates.io because the workspace uses unreleased git dependencies.

🏷️ Version Strategy

Version Format

The Interfold follows Semantic Versioning:

• Stable: v1.0.0 - Production ready
• Pre-release: v1.0.0-beta.1 - Testing/preview versions
  • -alpha.X - Early development, may have breaking changes
  • -beta.X - Feature complete, testing for bugs
  • -rc.X - Release candidate, final testing

Which Version Should I Use?

For Production (Mainnet)

Use stable versions only:

interfoldup install              # Latest stable
interfoldup install v1.0.0       # Specific stable version

For Testing (Testnet)

You can use pre-release versions:

interfoldup install --pre-release # Latest pre-release
interfoldup install v1.0.0-beta.1 # Specific pre-release

For Development

Build from source:

git clone https://github.com/gnosisguild/interfold.git
cd interfold
cargo build --release

🌿 Branch and Tag Strategy

Current Setup

• main - Latest code. All releases are tagged from here. Using feature flags for experimental features, we ensure that code is always stable.
• v*.*.* - Version tags for releases
• stable - Always points to the latest stable release

Installation Sources

# Latest stable release (recommended for production)
curl -fsSL https://raw.githubusercontent.com/gnosisguild/interfold/stable/install | bash

# Latest development version (may be unstable)
curl -fsSL https://raw.githubusercontent.com/gnosisguild/interfold/main/install | bash

📋 Release Checklist

For maintainers doing a release:

• Ensure all tests pass on main
• Review commits since last release for proper conventional format
• Decide version number (major/minor/patch)
• Create a release branch and run pnpm bump:versions X.Y.Z
• Merge the release pull request only after CI passes
• Update local main and run pnpm release:tag X.Y.Z
• Confirm the Release workflow passes before deployment
• Verify packages on npm
• Check GitHub release page for binaries and changelog
• Announce release (Discord/Twitter/etc)

🔧 Script Options

The bump:versions script supports several options:

# Prepare, commit, and push the release branch
pnpm bump:versions 1.0.0

# Prepare and commit without pushing the branch
pnpm bump:versions --no-push 1.0.0

# Skip git operations entirely
pnpm bump:versions --skip-git 1.0.0

# Dry run - see what would happen
pnpm bump:versions --dry-run 1.0.0

# Show help
pnpm bump:versions --help

# Tag the merged release from an updated main branch
pnpm release:tag 1.0.0

🔄 Rollback Procedure

If a release has issues:

1. Mark as deprecated on npm:

   npm deprecate @interfold/sdk@1.0.0 "Critical bug, use 1.0.1"

2. Fix and release a patch:

   pnpm bump:versions 1.0.1

📊 Version History

Check our Releases page for full version history and changelogs.

Security and Liability

This repo is provided WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

License

This repo created under the LGPL-3.0+ license.