Architecture

​

Overview

This page describes the high-level architecture for our cross-chain confidential transaction system that connects all EVM blockchains such as Arbitrum, Base, BNB, HyperEVM, Tempo, Ethereum, Stable, and Arc (as well as Stellar and Solana) to Fairblock’s Decentralized Cryptogrpahic Computer (FairyRing). This system enables confidential balances and transactions for tokens (e.g., stablecoins) issued or circulating on EVM chains without requiring changes to the underlying token contracts and without changing user wallet behavior. Confidentiality is achieved by offloading privacy-sensitive logic to FairyRing, while settlement and liquidity remain on the originating EVM chain. Confidential transfers use lightweight homomorphic calculations and fast zero-knowledge (ZK)-proof verification, executed within the protocol flow. The system does not rely on fully homomorphic encryption over the discretized Torus (TFHE) from an offchain coprocessor. All homomorphic calculations and ZK proof verification are extremely lightweight, and execution runs on FairyRing.

​

System at a Glance

The system is built with three layers: At a high level, the user journey runs through four stages:

​

Breaking Down the Layers

​

FairyRing: Decentralized Cryptographic Network

FairyRing operates as a dedicated confidentiality execution layer. Its core logic is implemented as Wasm contracts that maintain a confidential ledger of encrypted balances per account and per asset. These contracts process confidential transactions based on ZK proof verification and lightweight homomorphic encryption, ensuring that all balance updates are internally consistent while never exposing the underlying amounts. FairyRing also supports selective disclosure under defined conditions. Users decrypt their own balances locally with their own keys, while only encrypted amounts are stored onchain. When required for compliance, audits, or investigations, authorized parties can be granted access to scoped decryption keys. This is enabled by FairyRing’s MPC identity-based encryption (IBE), which allows specific accounts or transaction subsets to be revealed under well-defined conditions without introducing a single persistent audit key that compromises global confidentiality.

​

Gateway Contract

On each integrated chain, a dedicated gateway contract serves as the endpoint and local interface for users. Its primary functions are to lock and unlock tokens and to interface with the relayer. When a user deposits tokens, the gateway contract locks the funds and emits an event picked up by the relayer and sent to FairyRing. When a valid response is received from FairyRing through the relayer (for example, confirming a successful transaction or withdrawal), the contract updates its internal state and, in the case of withdrawals, releases the corresponding tokens back to the user. The gateway contract is intentionally minimal in logic. It handles token accounting and the relayer interface but avoids complex cryptographic operations. Cryptographic verification and homomorphic balance management are delegated to FairyRing.

​

Fairyport Relayer

The relayer moves encrypted messages between integrated chains and the decentralzied cryptographic network (not bridging funds). It is operated by Fairblock; partners are not required to run relayer infrastructure. The relayer is responsible only for transporting messages between chains and FairyRing. It does not perform cryptographic verification or balance management - that logic is delegated to FairyRing and the EVM escrow contracts.

​

Other Supported Chains

In addition to all EVM chains, Fairblock also supports Stellar, Solana, and other smart contract platforms using a similar architecture. Most of the infrastructure remains the same, with the primary differences being the gateway contracts and chain-specific integrations. Please contact the Fairblock team for implementation details and integration support.