Who should use the Secure Processing Framework?

Our SPF is designed to help any engineer (web2 or web3) bring privacy to their application, without having to run additional infrastructure or become a cryptography expert.

Furthermore, our goal is to support deployment of FHE-enabled programs directly to major chains. No L2, rollup, or new chain needed. As proof of concept, we currently support programs on Ethereum Sepolia and Monad (testnet). We’ll be integrating new chains (in testnet mode) soon.

We want to make our product as developer friendly as possible. If you run into any issues or need specific features, don’t hesitate to send us a message.

You’re a blockchain developer excited to build your latest dApp.

We believe that you should be able to deploy to any chain you desire; accordingly, our SPF enables doing exactly that.

Our unique architecture allows you to experiment with deploying to different chains, without having to rewrite your FHE program. To help you get started, we provide some starter code to assist with this process.

You’re a web2 developer excited to build one of your first dApps.

Creating end-to-end applications in a smart contract programming language like Solidity can be challenging.

Current restrictions on program operations are temporary (see limitations). Our goal is to enable developers to transform existing application code into privacy-preserving applications by simply adding annotations to indicate what data should be kept private.

The SPF architecture supports experimenting with different blockchains without rewriting application code. This allows you to write your application once and use it on any chain.

You’re a web2 engineer excited to bring privacy to your product.

Our offering is designed to be full service — handling storage, permissioning, and key management on your behalf. However, we have the flexibility to integrate with your existing storage provider or allow you to handle key management and permissioning if desired.

We know from experience how painful it is to have to rewrite application code; the SPF allows you to bring your existing C code (with some restrictions today) and transform it into privacy-preserving code by adding some annotations.