Skip to main content
This FAQ answers common operational questions for end users and institution admins about what end users can do in a Levery venue instance.

​
Onboarding and access

Access is granted only after these checks succeed:
  1. Verify email with a one-time code.
  2. Provide required personal details.
  3. Complete identity verification (KYC).
  4. Link a wallet and sign a message to prove ownership.
  5. Pass the institution’s activation policy (automatic or manual review).
The signature proves you control the wallet that will be used for permissioned access. It is not a transaction, does not move funds, and does not grant spending permissions.
It can appear as a KYC status from the verification provider (for example, Under review or On hold), or as the institution’s activation policy when manual approval is required. Access is granted only after approval.
Onboarding can be resumed without repeating completed steps. If your session expires, sign in again to continue. Switching devices can require revalidation of email or identity steps.

​
Account dashboard and assets

The Account Dashboard is the default landing view after authentication. It provides portfolio value, balances, liquidity position previews, and a transactions trail for the networks enabled by the institution.
Portfolio values, balances, positions, and activity are anchored to on-chain records such as transactions, events, and contract state. Fiat valuations use on-chain market price feeds so pricing inputs are verifiable, time-ordered, and audit friendly.
The base quote is the institution’s valuation reference used for consistent reporting across assets and networks. The display currency is a user-facing preference; values are converted from the base quote using oracle-backed FX pricing.
Levery is policy-scoped. It shows only the networks and assets enabled by the institution, while wallet apps often include additional networks and tokens. Fiat values can also differ due to pricing sources, update cadence, and rounding rules defined by venue policy.
The Assets page provides a detailed portfolio view with a top-line split of Positions, Spot, and Total Balance, an asset inventory table, and a By Network breakdown for chain-level reconciliation.

​
Pools and market data

These are operational indicators used for market selection:
  • APR is an annualized estimate derived from recent fee activity relative to current liquidity.
  • TVL is the total value locked in the venue’s display currency.
  • Volume 24h is the rolling 24-hour swap volume in the venue’s display currency.
They are indicative and not guarantees of future performance.
A dash indicates the metric is unavailable or not computed for the current snapshot. This commonly happens for new pools or during index refresh windows.
Pause controls prevent execution when incident response or operational maintenance is required. When a pool is paused, swaps and liquidity actions for that pool are rejected on-chain. When a venue-wide pause is active, all pools in the venue instance reject user execution flows until the pause is lifted.
Pools and Pool Stats can be viewed without a connected wallet. Swap and Invest execution requires a connected wallet and the wallet must be on the pool’s chain.

​
Swaps (Trade)

Exact input means you specify the amount to spend and the swap enforces a minimum output. Exact output means you specify the amount to receive and the swap enforces a maximum input. This choice also affects when service fees are charged.
Service fees apply only to swaps and are enforced on-chain. For Exact input, the service fee is charged from the specified input amount before execution. For Exact output, it is charged after execution based on the realized input delta.
ERC-20 swaps can require approvals before execution. Many venues use a two-layer allowance model: Token to a permit layer, then permit layer to the compliant router. Native-token swaps do not require ERC-20 approvals.
Swap execution requires a successful on-chain quote for the selected pool. Quoting can fail due to insufficient pool liquidity, RPC instability, misconfigured quoting infrastructure, or policy gating (for example, the wallet is not permitted for the pool or the pool is paused). When quoting fails, the UI disables execution to prevent submitting unpriced swaps.
Common causes include slippage exceeding tolerance, an expired deadline, insufficient balance, missing approvals, or on-chain policy rules rejecting execution.
Quotes are point-in-time estimates. Execution can differ when the pool price moves between quote and inclusion, or when dynamic LP fees adjust due to oracle-based deviation at execution time. Slippage limits bound acceptable execution; if the realized output or required input exceeds limits, the transaction reverts.
Settlement is bound to the initiating wallet. Proceeds cannot be redirected to arbitrary recipients, preserving custody and accounting controls.

​
Permissions and policy controls

Swap and liquidity eligibility is evaluated at execution time. If the institution revokes swap or liquidity permission, or changes the pool’s required role configuration, subsequent actions can be rejected on-chain until eligibility is restored. Spot balances remain in the initiating wallet; open liquidity positions remain associated with their token id and follow the venue’s policy for position management while eligibility is restricted.

​
Liquidity provisioning and positions

A position defines a minimum price and maximum price for a pool pair. It can be full range (maximally wide) or custom range (finite). The position is active when the pool price is within the selected range.
No. Liquidity positions are represented as non-transferable position tokens (soulbound). Ownership is fixed at mint time, and transfer entry points are disabled to preserve the venue’s compliance lifecycle controls.
LP fees accrue only when swaps execute while the position is in range. If the pool uses dynamic LP fees, the realized fee rate can vary under the pool’s configured logic.
If the current pool price is inside the selected range, both token amounts must be provided. Single-sided deposits are possible only when the price is outside the selected range.
Service fees apply only to swap execution flows. Liquidity events such as mint, increase, decrease, collect, or close do not include service fee deductions. Gas fees still apply.
End users can review position status, add or remove liquidity, collect accrued LP fees when available, and use position identifiers and transaction hashes for reconciliation.
Liquidity actions can be blocked by a disconnected wallet, wrong network, missing approvals, permission or role gates, pause controls, ownership verification, or limits and deadlines enforced at execution time.

​
Support and reconciliation

Authoritative records are on-chain. Transaction hashes, chain references, and contract state are the primary sources for reconciliation. UI values are indicative and follow the institution’s valuation policy.
The UI is backed by an indexing pipeline that streams on-chain events into the venue’s databases. Depending on chain finality, RPC latency, and indexer refresh cadence, recently confirmed transactions can take time to surface in dashboard balances, positions, or activity views. Transaction hashes remain the authoritative reference for immediate verification via external explorers.
Share the transaction hash and the pool and chain context. For swaps, include the pool pair and the attempted amount. For liquidity actions, include chain id, pool id, selected Min and Max, deposit amounts, and any approval transaction hashes.