Summary: Valantis is best understood not as one more DEX, but as a framework for building asset-specific DEXes whose pool behavior is composed out of modules. The core primitive is the Sovereign Pool: a base pool that can attach custom liquidity, fee, oracle, verification, and vault modules, with an optional pool manager deciding how much control remains mutable before revoking itself. Its first live product, the STEX AMM for stHYPE and similar redeemable yield-bearing assets, shows why the framework matters: instead of accepting generic-AMM losses, it routes around “loss versus unstaking” by using the native withdrawal path, dynamic fees tied to congestion, and optional lending of idle reserves. The reusable mechanism insight is that Valantis shifts the LP control surface away from one universal AMM invariant and into whoever controls module selection, pool-manager rights, withdrawal handling, fee updates, and protocol-level admin roles.
What it does:
Provides a modular protocol for building custom liquidity pools instead of forcing every asset into one generalized DEX design
Uses Sovereign Pools as base contracts that can attach liquidity, swap-fee, oracle, verification, and vault modules
Lets a pool manager set the liquidity module, configure fee and oracle modules, set pool-manager fees, and optionally revoke itself to make a pool immutable
Runs STEX AMM as an LST-specific AMM that uses native redemption queues rather than selling redeemable staking assets below fair value
Allows idle reserves in STEX pools to be deployed into lending modules for extra yield while keeping withdrawal logic tied to the underlying LST protocol
Uses stepwise dynamic fee logic that can increase when withdrawal queues are congested and reduce toward very low fees when redemption pressure is light
Key claims:
The docs say generalized DEXes are a poor fit for assets with special yield and redemption mechanics, and frame Valantis as a modular framework for building custom pools around those mechanics
The docs and core README describe Sovereign Pools as the backbone that hosts pluggable modules, making the protocol closer to a liquidity-kernel framework than to a monolithic AMM
The documentation’s query interface says practical pool-level authority sits with the optional poolManager, which can set liquidity, fee, and oracle modules and later revoke itself to lock the configuration
The same docs say protocol-level privileged operations are still handled by multisig or role-admin controls, with no active onchain veto mechanism and no protocol-wide onchain upgrade-timelock guarantee for proxy upgrades
The STEX materials say the pool is designed so an LST is not sold below true value; instead, the protocol can use the native withdrawal mechanism and charge dynamic fees that reflect queue congestion
The STEX docs say withdrawal modules, lending modules, and swap-fee modules can each be updated through timelocked owner actions, which makes the protocol’s economic edge inseparable from its admin and keeper control surface
The STEX repository README makes the trust surface unusually legible: multisig-controlled owner roles can upgrade lending integrations, route reserves into external lending protocols, control withdrawal flows, and update fee parameters, with explicit documentation of insolvency, liquidity, and accounting risks
Whitepaper: The clearest primary paper is the official STEX AMM whitepaper, supplemented by the official docs and public repositories; see ../whitepapers/valantis-primary-sources-2026-05-08.md.