Fairblock lets any application add confidentiality without exposing private data onchain. The cryptography an app relies on can differ, for example 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 (Application Layer)

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

Gateway Smart Contracts (FairyKit)

The gateway contract receives and stores encrypted messages or transactions on the integrated chain. FairyKit provides these contracts for the network being integrated.
3

Relayer Layer (FairyPort)

The communication layer that listens to the gateway and forwards encrypted state or inputs between the integrated chain and Fairblock, coordinating decryption and execution. FairyPort and IBC are examples.
4

Decentralized Cryptographic Network (FairyRing)

FairyRing processes the compute request: it performs the confidential computation and/or generates the private key, then returns the result. These computations are onchain and verifiable, not a centralized offchain server.

​
How Integrations Differ: FairyKit vs Co-Processing

The four components above are constant, but where the decryption and execution actually happen can vary. There are two main routes:
Integration packages specific to the chain being integrated, allowing custom setups in which the partnering network carries out some or all of the decryption and execution itself.Available for Cosmos, EVMs, and RustVMs. Fairblock can integrate with any network.

​
Apps Hosted on FairyRing vs External Chains

FairyRing is itself a Cosmos chain, so the same four-layer flow applies whether an app lives natively on FairyRing or on another chain:

Native FairyRing Apps

Confidential computation and contract callbacks are native functions of the chain, so no external relayer is needed and return steps happen internally. Native apps benefit from more performant operations.

External Chains

The relayer layer (FairyPort or IBC) bridges the integrated chain and Fairblock, while FairyKit supplies the gateway contracts. FairyRing integrates frictionlessly with any chain, deepening liquidity and making the network more robust.

​
Next Steps

All of these integration methods provide the same ability to interact with Fairblock, with your own application logic layered on top. Once you have this high-level picture, head to the quick-start tutorials for the chain you’re working with:

Confidential Transfers

Get started with encrypted amounts and balances on public blockchains.

Pre-Execution Privacy

Explore sealed-bid auctions, private governance, and encrypted transactions.