Skip to content
DAMREV
Start a Structuring Review

Named engine · Financial infrastructure layer

Flux

Designed to route a non-custodial swap to $DREV.

Flux is designed to let a user swap USDC into $DREV without handing over custody, once $DREV exists and the permissions the swap needs are in place. It would present the swap, route it on the Stellar decentralised exchange, and leave the keys in the user's Vault throughout.

Flux performs routing as a function; it is not an exchange, broker or venue.

$DREV has not been minted, issued, offered or sold, and no swap into it or staking of it is available.

What it does

What does Flux do?

Flux is the liquidity and swap engine. It is designed to present and route a swap from USDC to $DREV on the Stellar decentralised exchange, with no minting at swap, while the user keeps custody. It depends on Conduit for incoming USDC and on Vault for keys.

  • USDC to $DREVDesigned for a swap from USDC into $DREV on the Stellar decentralised exchange. Not available.
  • User-held custodyKeys stay in the user's Vault from the first step to the last.
  • Route, not venueFlux routes the swap; it does not operate the market it routes to.

How it works

How does Flux work, step by step?

Three steps, each with one job.

  1. Step one

    Presents a swap

    Flux would show the user a USDC to $DREV swap before anything moves.

  2. Step two

    Routes on the exchange

    The swap would route through the Stellar decentralised exchange, and no token would be minted at swap.

  3. Step three

    Keeps the user in custody

    Keys would stay in Vault and the user would sign, so custody never passes to DAMREV.

Where it fits

Which engines does Flux depend on, and which use it?

Flux sits in the financial infrastructure layer, between the on-ramp and governance. It depends on two engines, and one engine depends on it.

Conduit supplies USDC: a user brings fiat in through the licensed provider, and Conduit hands the USDC on. Vault supplies custody on the user's side, since keys remain in the non-custodial wallet, and Vault lists Flux among the engines that rely on it.

Quorum is designed to take $DREV from Flux: a holder could stake it through Quorum for governance rights over platform parameters. Sentinel checks the transfers Flux would attempt, and Sentry supplies the user's device-bound signature. Reserve draws on Flux for treasury liquidity, and Flux reads Equilibrium's model.

Standards and integrations

Which standards and networks does Flux work with?

  • StellarSwaps would route on Stellar, where any account can issue an asset natively and each ledger closes roughly every five seconds with finality at close1. A completed swap would not wait on later confirmation.
  • USDC and the GENIUS ActUSDC is issued by Circle, not by the group. The GENIUS Act, signed on 18 July 2025, sets one-to-one reserve rules for payment stablecoin issuers and takes effect on the earlier of 18 January 2027 or 120 days after final regulations2.

Controls

What does Flux enforce, and what does it never do?

Flux enforces

Flux is designed to enforce custody: the user would hold the keys at every step and sign the swap on their own device.

Flux never

  • Takes custody
  • Mints at swap
  • Acts as an exchange, broker, or regulated venue
  • Promises a rate, a price, or the depth of the market it routes to

Common questions

What do people ask about Flux?

Short answers to the questions people ask most about this topic.

Is Flux an exchange?

Flux is a routing engine: it presents a swap and routes it on the Stellar decentralised exchange. It is not itself an exchange or a regulated venue.

Would I keep custody during a swap?

Yes, by design. The user would keep custody, with keys held in Vault, and nothing would be minted at swap.

What rate would I get?

Flux would show the swap as the Stellar decentralised exchange offers it before the user signs. It makes no price or rate promise.

Can I swap into $DREV today?

No. $DREV has not been minted, issued, offered or sold, and no swap into it is available. This page describes the engine's design.

References

  1. 1.Chainstack, "What is Stellar". https://chainstack.com/what-is-stellar/ Also: Stellar developer documentation, "Control access to an asset", https://developers.stellar.org/docs/tokens/control-asset-access
  2. 2.Greenberg Traurig, "GENIUS Act enacted, establishing a regulatory framework for payment stablecoins". https://www.gtlaw.com/en/insights/2025/7/genius-act-enacted-establishing-a-regulatory-framework-for-payment-stablecoins-issued-or-sold-in-the-united-states

Last updated:

Ready to build on programmable infrastructure?

Tell us what you want to tokenize. We will show you how DAMREV can run it.