The swap screen was already open when I noticed the first bad sign: I was looking for ParaSwap, but the product was calling itself Velora. That is exactly the kind of rename that catches people who have been burned before. You assume the old token, old app, and old instructions still line up; then you sign an approval for the wrong asset or follow a stale migration thread.
The useful change is that ParaSwap has moved beyond being only a “find the best route right now” swap aggregator. The interface now exposes time-weighted trading alongside regular swaps, limit orders, and OTC-style execution. For a larger trade, that opens a practical option: split the order over time instead of pushing all of it through one block and discovering too late that the displayed quote was not the price you actually moved.
The catch is the name, not the route
ParaSwap’s PSP token migration to Velora’s VLR token is the part worth settling before doing anything else. A wallet can still show an old PSP balance. A search result can still use the old brand. Neither tells you that a random contract, token page, or “migration helper” deserves an approval.
I stopped treating the name as proof and worked from the transaction outward. First, choose the chain and the token pair. Then inspect the quoted route: which assets are being spent, what minimum amount arrives, and whether the trade is immediate or scheduled. At that point, use the ParaSwap reference to check the current ParaSwap context before connecting a wallet. The page is useful here because the question is no longer “which logo looks familiar?” but “what am I actually about to authorize?”
The path that finally worked
- Use a small test amount first—small enough that a mistaken network or token selection is annoying, not expensive.
- Read the approval request separately from the swap. The spender address and allowance matter more than the polished quote.
- For an immediate swap, compare minimum received against the amount you can live with. For a larger order, use the time-based option only after confirming its schedule and cancellation terms.
The new capability is not a reason to automate trust. It is a better execution choice once the basics are visible: the right chain, the right token, a bounded approval, and a route you can explain in one sentence. That is enough to make ParaSwap’s evolution useful without pretending that a rebrand erased the old failure modes.