Key Concepts-old

Pay(ID)

A unique, human-readable identifier that can receive any stablecoin from any chain, and automatically route it to the recipient’s desired destination.

Routes

Rules defined by the user to control how funds are settled. Routes follow an "if this, then that" model. Examples:

• USDC from Optimism → USDC on Base, into Wallet A

• Any funds from alice(id) → USDT on Polygon, into Wallet B

Routes can be based on 3 types of triggers:

• Source Token (e.g. if I receive USDC, then...)

• Source Network (e.g. if I receive funds on BNB Chain, then...)

• Sender (e.g. if I receive funds from Bob, then...)

Pay(ID) Data Layer

Reveel’s database layer storing:

• Pay(ID) registrations

• Routes

• Linked wallets

• Metadata (linked ENS, MocaID, email, social handles, app namespaces…)

Liquidity Orchestration Layer

Reveel’s routing engine that determines the optimal transaction path using partner liquidity networks. It finds the best route to deliver funds to the destination wallet, considering:

• Gas fees

• Available bridges

• Partner fees

• Settlement time

• Token liquidity