Fairblock is a decentralized confidentiality network that provides cryptographic services and confidential application infrastructure across multiple chains and execution environments. FairyRing coordinates Fairblock’s decentralized cryptographic services; users and partners access Fairblock through supported chains, applications, SDKs, and APIs without needing to interact directly with the underlying network. Fairblock lets any application add confidentiality without exposing private data onchain. The optimized cryptograhic scheme an app relies on can differ based on the application, for example MPC, identity-based encryption, or homomorphic encryption, but the top-level architecture is the same. This page describes that shared architecture: the four components every integration passes through, and the end-to-end flow of an encrypted message from the user to Fairblock’s cryptographic network and back to the integrated blockchain.
This page stays intentionally generic. We talk about “encrypted messages” and “private keys” rather than scheme-specific concepts. The deeper mechanics of each cryptographic approach live in the product-specific sections.

​
The Four Components

Every Fairblock integration is built from the same four layers:
1

Encryption SDK

The Encryption SDK runs in the user’s application (front-end, wallet, or app) and encrypts private inputs locally before anything touches a chain, also generating a zero-knowledge proof where one is required. Encryption and proof generation happens end-to-end on the client side and does not rely on any third party.
2

Gateway Smart Contracts

The Gateway smart contracts receive and store encrypted messages and transactions on supported chains. They enable users and applications to leverage confidential computing directly on their existing chain, without bridging assets, creating a new address, or using a new wallet.
3

Relayer Layer (or FairyPort)

The message passing layer that listens to the gateway and forwards encrypted state or inputs between the integrated chain and FairyRing, coordinating confidential execution and verification.
4

Decentralized Cryptographic Network (or FairyRing)

FairyRing processes the compute request: it performs the confidential computation operations such as HE, ZKP verfication, DKG, or generating decryption keys then returns the result. These computations are onchain and verifiable, not a centralized offchain server or optimistic coprocessor.

​
Apps Hosted on FairyRing itself or Integrated Chains

FairyRing is primarily designed as a decentralized confidential computing layer with maximum flexibility for developers and users. FairyRing can seamlessly deliver confidential computing to existing chains and applications, or host applications natively. The choice depends on the desired tradeoff: frictionless integration and compatibility with existing ecosystems, or faster and lower-cost native execution.

Native Execution

Confidential computation and contract callbacks are native functions of the chain, so no external relayer (FairyPort) is required. Requests and callbacks remain entirely within FairyRing, resulting in faster execution, lower costs, and a simpler architecture.

Apps on Integrated Chains

FairyPort connects integrated chains to FairyRing (Decentralized Cryptographic Network). This enables applications to add confidential computing without requiring users to bridge assets, create new wallets, or migrate to another chain, preserving the existing user experience while adding privacy and confidential execution.

​
Next Steps

Now that you have a high-level understanding of the architecture, continue to the documentation for the cryptographic technology and application you’re building with:

Confidential Transfers (Homomorphic Encryption)

Explore confidential assets, stablecoins, payments, treasury, payroll, and yield.

Pre-Execution Privacy (MPC-IBE)

Explore sealed-bid auctions, frontrunning protection, encrypted predictions, and private governance.