Skip to main content
RapidX enables seamless cross-chain swaps while ensuring decentralization at every step. It overcomes major challenges in the current ecosystem, such as high costs, latency, messaging fees, centralized oracle fees, and centralized relayer fees, by introducing a modern architecture. This architecture leverages zk-proofs and BNB Greenfield to validate transactions directly on-chain, eliminating reliance on centralized intermediaries and providing fast, low-cost, and fully transparent cross-chain transfers.

​
Architecture

title

​
Cross-Chain Transaction Flow

Let’s take a cross-chain transaction example where a user wants to bridge PEPE tokens on Ethereum to BNB tokens on the BNB Chain.

​
1. Quote Retrieval

The user initiates the process by requesting a quote from the Rapidx system for the swap (e.g., PEPE on Ethereum → BNB on BNB Chain).

​
2. User Accepts and Submits the Transaction

Once the user accepts the quote, a transaction is submitted to a Rapidx smart contract deployed on Ethereum. This contract receives the PEPE tokens and triggers the bridging logic.

​
3. Swap via DEX or Market Maker (On-Chain Execution)

The Rapidx smart contract interacts with decentralized exchanges or market makers to convert PEPE into a stablecoin or native asset (like ETH or USDT), choosing the best available rate. A transaction log is emitted on-chain that includes the quoteId and swap details, ensuring transparency and traceability.

​
4. Validators Sign Using TSS

Rapidx validators continuously listen to the Ethereum transaction log. Each validator independently signs the quoteId and swap details using Threshold Signature Scheme (TSS). These signatures are collected and passed to a ZK prover circuit in parallel, improving efficiency and speed.

​
5. Circom ZK Circuit Generates Proof

The Circom zero-knowledge circuit aggregates the TSS signatures and generates a ZK-SNARK proof verifying that the validator quorum has reached consensus. This proof is cryptographically sound and privacy-preserving.

​
6. Proof Stored on BNB Greenfield (Public & Verifiable)

The ZK proof is stored on BNB Greenfield, a decentralized, publicly accessible storage layer. This makes the consensus verifiable by any third party, ensuring decentralization and auditability.

​
7. Executor Verifies and Finalizes on BNB Chain

The Executor continuously monitors BNB Greenfield. When a new ZK proof is detected, it is fetched and verified on-chain (or optionally off-chain for cost savings). Once verified, the Executor calls a smart contract on the BNB Chain to release BNB tokens to the user or execute the final leg of the swap. Ensuring validator consensus through cryptographic guarantees rather than trust.
⌘I