Security

Security at lp.xyz

lp.xyz is non-custodial: it builds each transaction and a wallet you control signs it. The keys to the wallets it creates for you sit in Turnkey's enclave under your own sub-organization, and you can export them any time.

In short

Without automation, lp.xyz cannot move your funds. With automation on, it can sign for the one wallet you delegate. In the current policy version that permission is not limited to particular programs or contracts by the key policy: lp.xyz's own checks hold it to the supported actions and your settings, so a compromise of the automation service could put the assets in that wallet at risk. Revoking removes future signing once it takes effect, but can't cancel a transaction that was already signed or sent.

lp.xyz has not published a third-party security audit of its contracts yet.

Who holds the keys?

You do. Every account is its own Turnkey sub-organization, created the first time you sign in, and each kind of wallet keeps its key in a different place:

  • Trading wallet. Created for you at sign-up: one seed with a Solana address and an EVM address. Its keys are held in Turnkey's enclave under your sub-organization, and your signed-in session approves each transaction.
  • Imported wallets. Keys you bring in yourself, held the same way and signing the same way.
  • External wallets. Phantom or Solflare on Solana, MetaMask or any injected EVM wallet. You sign each transaction in the wallet's own UI, and lp.xyz never sees the key.

Embedded keys are exportable. The export opens in Turnkey's hosted window, where the key is shown and copied; the app never reads it. If you signed up with email or Google, the app asks you once to back the key up, because nobody at lp.xyz can recover it if you lose access. See sign in and multi-wallet.

What can lp.xyz do with your funds, and what can't it?

lp.xyz can build transactions and hand them to your wallet to sign; it cannot sign them for you unless you turn on automation. It also cannot undo a signature, recover a lost key or stop a token from falling.

  • No pooled funds. lp.xyz has no vault: every wallet signs its own transactions, and lp.xyz only builds them.
  • Costs before you sign. Every platform fee, such as 0.25% on liquidity, is already in the quote you approve and settles in the same transaction as the action. See fees.
  • Signed transactions are final. Being non-custodial means nobody, lp.xyz included, can reverse a transaction you approved.

What can automation do on your behalf?

It acts on the one wallet you delegate. Turning automation on is two steps: you accept the terms, then delegate signing. That creates a credential inside your own account that can sign for one wallet address, and the server checks it works before recording the grant.

The key policy behind that credential limits it to that wallet, not to particular programs or contracts. The limits on what it signs live in lp.xyz's automation code: on Solana it checks who pays for each transaction, on EVM chains it only signs calls to an allowlist of contracts for the action, and every job runs only the strategy you set. Those checks run on lp.xyz's servers, so they protect you only as long as those servers are not compromised.

  • Your rules, your limits. Harvest only fires above your threshold, and on EVM chains only under your gas ceiling. A wall that follows price waits out a dwell window and has a cap on moves per day.
  • Every action is on the record. Each automated action lands in your activity feed with its signature, and a failed run records why it stopped.
  • Revoke any time. Revoking removes the credential, so nothing new is signed once it takes effect; a transaction already signed or sent can't be called back. Archiving a wallet parks every job on it without losing your settings.

Automation maintains a position; it doesn't judge whether you should be in it, and a trigger can execute at a different price from its level. See automation.

How does lp.xyz check pools and tokens?

Every pool shown gets a pool audit, a versioned check of its identity, token controls, hooks, fees and liquidity, rolled into one verdict from Blocked to Eligible. A Blocked pool takes no new deposits, while existing exits stay open. Token pages show the signals behind most losses: mint and freeze authorities, liquidity depth and locks, holder concentration, and age and activity.

When a check can't be answered, lp.xyz says it doesn't know rather than showing a pass. A pool audit is lp.xyz's check of a pool, not a security audit of lp.xyz. See pool audits and risks and safety.

Which contracts does lp.xyz use?

On EVM chains, lp.xyz's one execution contract is LpxyzFeeRouter, deployed in the v1 release on 13 October 2026 (UTC) (Uniswap v4 swaps use each chain's own UniversalRouter). It accepts a short-lived plan signed by lp.xyz's policy key and submitted by your own wallet, pulls only the inputs that plan declares, runs the AMM calls, pays the platform fee, clears every token allowance it set and refunds the rest. Action and fee share one transaction, so if any part fails the whole thing reverts. The same release deployed a platform-fee hook and a FarmStream contract, neither of which is in use yet.

On Solana, liquidity actions call each AMM's own program. The one Solana program in lp.xyz's codebase, the marketplace escrow, is not deployed to mainnet, and the marketplace is off.

Has lp.xyz been audited?

No third-party security audit of lp.xyz's contracts has been published yet, so treat LpxyzFeeRouter as unaudited. The AMMs you provide liquidity to run their own programs and contracts, under their own audits.

Start provisioning.

Connect a wallet and LP across 6 AMMs on Solana and EVM from one place.