Velora exchange profile

Velora, previously ParaSwap, combines a public swap interface with execution infrastructure used by other applications. Its distinguishing feature is the choice between signed trading instructions filled by competing solvers and a conventional transaction routed through decentralised liquidity. The same brand also covers scheduled trades and bilateral OTC settlement. Those routes have different funding, cancellation and gas requirements.[2]

DefiLlama displayed approximately US$1.208 billion of rolling 30-day DEX aggregator volume on 20 October 2026. Its underlying snapshot at 19:37:32 UTC recorded US$1,208,268,680. This is spot-token value routed through Velora: it overlaps activity on the venues supplying liquidity and cannot be added to their turnover as separate economic trading. It does not establish the number of individual active traders.[40]

For a broader reach claim, Velora’s homepage advertises more than 30 million trades and US$160 billion in cumulative volume, without a clear measurement cut-off. Those issuer totals use a different scope from the independent rolling series. The homepage addresses individual traders, institutions and developers; a registered-user or verified monthly-person count was not established.[1]

A Delta order binds the owner, beneficiary, tokens, quantities and validity conditions. Settlement must satisfy the signed terms. The solver model can improve the achieved output, but a submitted order is not yet a completed transfer. Market execution instead depends on the transaction being included successfully; a reverted transaction can still consume network fees.[10]

Portikus runs a sealed-bid process: participating solvers do not see competing bids while they commit their executable offers. Selection concerns the return available for that specific order. This design reduces opportunities to copy or react to exposed order flow; it does not guarantee a fill, eliminate adverse price movements or turn every Market route into a protected Delta route.[11]

The April 2025 terms still describe free access.[33]

The later interface tariff, dated 16 February 2026, discloses charges for most swaps.[28]

Fee illustration: at an unchanged US$10,000 trade value, 0.15% is US$15, while 0.01% is US$1. These are interface-fee components only. The illustration excludes liquidity-provider charges, price impact, network fees, bridge costs and market movement; it does not estimate the all-in cost of a specific quote.[28]

The quote needs to be read as an exchange of specified quantities. A route that consumes shallow liquidity can deliver a worse rate even when its explicit charge is small. Slippage tolerance sets an acceptable execution boundary around the quote; price impact describes how the proposed trade itself changes the obtainable price. They are different quantities.[3]

At the published 20% annual discount, Basic costs US$4,800 for a hypothetical year versus US$6,000 monthly-billed: US$1,200 less, excluding tax and separate charges.[14]

Velora Portal, announced on 5 October 2026, centralises API plans, application keys and team access. Card billing uses Stripe; USDC payments use Request Finance. The USDC route requires payment of renewal invoices rather than an assumed automatic wallet debit. Application analytics and billing belong to this business account layer.[30]

Trading usually begins with assets already held in a compatible wallet. An ERC-20 approval authorises a particular spender on a particular chain; Delta, Augustus and AugustusRFQ are separate contracts. Approving the Market router does not authorise a Delta trade. A supported permit can replace a standalone approval, but it remains a signed spending permission with its own limits. ERC-20 limit orders and TWAP require on-chain approval for the total commitment.[15]

dETH can be unwrapped 1:1 through withdrawNative, specifying amount and recipient in an on-chain transaction. Withdrawing funding from an open order can prevent settlement.[16]

The order-history schema separates expected amounts from executed amounts, records source and destination transaction hashes, and attaches a bridge refund only after its transaction receipt has been verified. Some bridge providers do not return source-token refund metadata. A missing field is therefore not evidence of a completed refund; the transaction record remains relevant.[20]

Velora’s decentralised model leaves wallet keys with the user, while approved contracts acquire specific powers to move tokens. An unused allowance can outlive a browser session. A signature that authorises an order, a token allowance and a connection to a website are separate permissions; disconnecting the interface does not revoke the other two.[15]

A vulnerability affected Augustus V6 on 20 March 2024. The current recovery article, updated in July 2025, describes whitehat rescues and individual Safe accounts for affected wallets that had not revoked by the specified June 2024 cut-off. It instructs affected owners to remove the old allowance before moving recovered funds. This is a remedy for a particular contract incident, not evidence that every loss was repaid or that standing insurance covers later versions.[32]

Old and current router versions must be identified accurately during recovery. The migration documentation says v5 and v6.1 remain operational while new API integrations use Augustus v6.2. Delta API V1 and V2 share the same on-chain contracts. An API-version change therefore does not, by itself, prove that the spender address or custody mechanism has changed.[23]

Connecting a public wallet does not make the service anonymous. The privacy policy covers IP information, public addresses, transaction information and messages supplied to support. Public-chain records can remain visible independently of what the interface retains. A data deletion request and reversal of an on-chain transaction are different operations.[34]

For an ordinary service complaint, the terms provide [email protected]. Disputes fall under BVI law and BVI-IAC arbitration in English, normally in Road Town with three arbitrators, unless otherwise agreed. These contract terms are separate from the privacy policy’s CNIL route for data-protection complaints.[33][34]

The inspected material did not establish a universal support-led recovery hold, password reset or dormant-account fee for wallet trading. Wallet access is controlled by the chosen wallet. For a continuing order, the meaningful end points are completion, expiry or valid cancellation; an inactive browser or disconnected device is not an instruction to stop execution.[19]

The terms name Laita Labs Ltd for the Velora Foundation; they establish neither incorporation nor a financial permission. BVI governing law proves neither.[33]

The protocol’s administrative structure is more specific than an assumption that all decisions are made by token-holder votes. Under the adopted PIP-77 framework, routine operations sit with the Foundation and Laita; token-holder governance is retained for structural matters involving VLR. Technical administration and a permission from a financial regulator remain separate questions.[36]

The ParaSwap-to-Velora transition is treated here as one continuing exchange identity. The September 2025 VLR announcement described a 1:1 migration from PSP and a bonus window ending on 16 December 2025. Those historic migration incentives are not a current joining bonus.[37]

PIP-77 preserved claims on previously earned, unclaimed rewards and specified continued withdrawal-interface availability for at least a year after approval. The older staking and VLR marketing pages must therefore be read alongside the April closure. Staking is not listed as an active service in this profile’s operator record.[36]

Operator

Laita Labs Ltd, representing the Velora Foundation

Exchange model

Decentralised

Service scope

Wallet trading through Delta and Market, with limit, TWAP and bilateral OTC instructions.

Client types

Retail clients; Institutional clients

Pricing publication

Public and quoted pricing

Other names

ParaSwap; Paraswap

Pricing scope

Published interface and API rates; actual route and partner charges vary.

Funding scope

Wallet-held tokens; native Delta deposits and route-specific bridging.

Custody and asset handling

Users retain wallet keys; approved contracts and funded native orders have distinct asset-control powers.

Client eligibility

Adult eligible users; territory, sanctions and incentive restrictions apply.

Support

Help Centre, explorer, status resources and a business contact form.

Authorisation and registration scope

No entity-specific financial permission established from the inspected contract.

Exchange metadata checked 20 Oct 2026Source 1Source 33Source 4Source 36

Velora exposes APIs, an SDK, an embeddable widget and an MCP server for agents. These are integration surfaces, not evidence that the platform manages a discretionary portfolio for every connected user. The developer must choose the execution mode and preserve the user’s amount, beneficiary and validity constraints when preparing an order.[24]

The guide’s simple agent chooses Market for native-token sales; that is a limitation of the example, not evidence that Delta cannot sell native ETH. The current native-token documentation supports the extra deposit route. Similarly, the tools can relay signatures without creating them. Keeping those distinctions explicit avoids overstating either the server’s powers or the protection supplied by a front-end prompt.[39]

For integrations, Velora’s decision tables require explicit chain and token identity, retain sell-versus-buy semantics, and stop after a declined signature. A route change, new recipient or higher spending limit requires a corresponding authority decision. These are documented integration rules; this profile has not connected a wallet, run the sample agent or tested live execution.[27]