Documentation

FLUX Pay is a non-custodial privacy layer built on top of Solana that enables privacy-oriented token transfers. Unlike basic direct sends, FLUX Pay uses an Ephemeral Routing Protocol (ERP) to route through short-lived routing accounts to make simple address-to-address traceability harder.

FLUX Pay focuses on practical on-chain privacy improvements (like multi-hop routing and timing jitter). It is not a guarantee of perfect anonymity, and privacy properties depend on how you use the protocol and the broader on-chain context.

The FLUX Privacy Chain is our core innovation—a secondary transaction layer that operates on top of Solana's base layer. When you initiate a private transfer, your funds enter our Privacy Chain where they route through ephemeral hops to reduce simple correlation.

How Privacy Chain Works

• Ephemeral Routing — Your transfer routes through short-lived routing accounts to help reduce simple input/output correlation
• Multi-hop Routing — Funds route through a short chain of ephemeral hops to reduce direct address-to-address traceability
• Temporal Obfuscation — Randomized delays between 0.5-3 seconds are introduced at each hop to help reduce simple timing correlation
• Operational Safety — Routing is designed to be non-custodial and minimize the amount of sensitive data handled by the frontend

Privacy Guarantees

FLUX Pay provides two modes of operation: AI Assistant for conversational transfers with wallet connection, and Non-Custodial mode (no wallet connect).

Our Ephemeral Routing Engine (ERE) is the backbone of FLUX Pay's privacy infrastructure. It coordinates the creation and use of short-lived routing accounts that are used to route transfers through multiple hops.

Technical Architecture

• Managed Routing Keys — Routing accounts are created and used for multi-hop transfers, with signing handled by a managed wallet provider (so private keys are not exposed to the browser).
• Deterministic Destruction — After a wallet completes its routing duty, its key material is retired from active use and rotated out of circulation.
• Routing Randomization — Routing parameters include randomized hop counts and timing jitter.
• Step-Based Execution — Transfers execute as a series of steps with status tracking, so failures can be detected and handled.

Routing Parameters

Use these commands with our AI Assistant for quick actions:

A 1% protocol fee is deducted from the transfer amount to support protocol development and infrastructure costs.

Security is paramount at FLUX Pay. Our infrastructure has been designed from the ground up to protect user funds and privacy at every layer.

Security Measures

• Non-Custodial Design — We never have access to your funds. All routing is performed through user-funded routing plans and server-side execution, not custody transfers
• Defense-in-Depth — We validate inputs, use strict allowlists where possible, and design server routes to avoid secret exposure
• Minimal Data — We store only what's needed to execute and track routing plans; on-chain transactions remain publicly visible
• Encrypted Communications — All API communications use HTTPS
• Operational Controls — Production deployments should use rate limiting and monitoring appropriate for your environment

FLUX Pay is designed for legitimate privacy use cases. We believe financial privacy is a fundamental right, but we also take compliance seriously.

Our Approach

• OFAC Screening — All destination addresses are screened against sanctioned wallet lists in real-time
• Transaction Limits — Reasonable limits prevent abuse while allowing normal privacy-conscious users to transact freely
• Legitimate Use Focus — Our service is designed for salary privacy, business transactions, personal security, and other lawful purposes