White-Label Permissioned Market Infrastructure
Define who can trade, who can provide liquidity, how each market operates, and when activity must pause. Levery provides the on-chain liquidity infrastructure while your institution retains the brand, participant model, market policy, and operating authority.
Your Institution
White-label deployment
$2.71B
Total Volume (1M)
XRP LedgerVolume in USD
Fees in USD
The institution defines eligible participants, approved assets, required roles, fees, and pause procedures. Levery provides the market, execution, and position technology, and never acts as market operator, liquidity provider, or guarantor of market performance.
Controlled participation
Permissioned Liquidity Pools combine public price discovery with controlled execution. Institutions can create markets for approved assets while keeping participation, roles, and market configuration aligned with their operating model.
Only the configured institution authority can initialize a pool under its market deployment. Define the approved asset pair, participant structure, role requirements, fee parameters, and optional external price reference for each market.
Authorize each account separately for trading and liquidity provision. A participant can trade, provide liquidity, perform both activities, or remain outside execution until the appropriate permission is granted.
Apply deployment-wide eligibility, then require an institution-defined role for a specific pool. Roles can represent participant class, jurisdiction, product eligibility, or another approved operating mandate without treating the contract as the source of identity or compliance decisions.
Allow participants and applications to request non-mutating quotes before they are eligible to execute. State-changing swaps still pass through the configured router and hook, where current permissions, required roles, amount limits, deadlines, and pause state remain decisive.
Segregated position ownership
Approved liquidity providers can create full-range or concentrated positions with explicit price ranges, slippage limits, and transaction deadlines. Each position is funded and authorized by its owner's wallet.
Represent each position through a non-transferable on-chain record with owner, pool, range, fee tier, and state metadata. The position cannot be transferred to another account and remains linked to its original owner until closure.
Only the recorded owner can increase or remove liquidity, collect fees, close the position, or burn its record. Current permissions and pause state still apply, so the institution must define clear procedures for revocation, freezes, remediation, and exceptional access.
Market-level controls
Market control view
Illustrative market parameters
Operating state
Policy connected
Illustrative operational view. Institutional policy and authorized actions remain deployment-specific.
Coordinate individual KYC, business KYB, wallet screening, verified account ownership, and company membership through institutional systems and connected providers. The contracts do not perform those checks. They enforce the permission state supplied by authorized operators.
Grant or revoke independent swap and liquidity permissions and assign pool-specific roles after the relevant institutional review. Off-chain status or screening results do not change on-chain authority without an explicit permission action.
For routed swaps, the submitting account is also the payer, receiver, and permission identity. This makes the account being checked, funded, and settled explicit, while limiting execution patterns that separate those roles.
Review permissions, swaps, positions, liquidity activity, fees, pool configuration, and administrative events through connected operational views. Indexed records support monitoring and reconciliation but remain subject to confirmation and processing latency.
Launch a permissioned liquidity market your institution can configure, govern, and operate.