What our server holds
- Your login ID, and the email address that Privy has for your login.
- Your wallet address.
- Your settings and your copy list.
- Records of your positions, transactions and withdrawal requests.
- The key of LP-Mimic’s own trading permission. Privy lets this key sign only what the rules below allow. Those rules have a limit, which this page also describes.
What our server does not hold
- The private key of your wallet. It stays with Privy. You can see it only in Privy’s own export screen.
- Your email codes. Privy sends and checks them.
Protections in LP-Mimic
Login
- You log in with a code sent to your email. There is no password to steal.
- A security check from Cloudflare can show before a code is sent.
- Addresses with a
+tag and addresses from throwaway mail services are refused. - Each new login waits for our approval before it can set up a wallet.
- A session ends 7 days after you log in, or after one day without use.
- Our server checks your login on every request. A request can reach only your own account.
Your wallet
- You own the wallet. Only you can export its private key, and only in Privy’s own screen.
- During setup, the wallet page removes any other access from the wallet. After setup, only you and LP-Mimic can use it.
- LP-Mimic trades with a trading permission that works only within fixed rules. Privy holds these rules and refuses any transaction outside them.
What the rules allow
The rules allow the trading permission to sign these actions:- Transactions with Meteora DLMM, the Jupiter swap program, and two Solana helper programs (network fees and transaction notes).
- SOL transfers to your own wallet or to your wallet’s wrapped SOL account.
- Small SOL payments, capped at 0.001 SOL each, to a service that delivers transactions to Solana.
- Token accounts created for your wallet, and token account closes that pay the rent back to your wallet.
- Token burns by your wallet, and updates of your wrapped SOL balance.
- For tokens with a transfer fee: moving the fee that a token account holds back to the token’s own mint account.
Checks before every signature
Our server checks each transaction before the trading permission signs it:- Every instruction must be on the allowed list above.
- A Jupiter swap must pay into your own accounts, spend the planned amount, stay within the slippage limit and take no platform fee.
- The fee payer must be your wallet, and the priority fee must stay under the limit that LP-Mimic sets for every account.
Withdrawals
- No key of LP-Mimic signs a withdrawal. You sign each withdrawal yourself on the wallet page.
- The wallet page asks for a new email code on each visit. A withdrawal is confirmed only by a login that started after you asked for it.
- Before you can approve, the wallet page checks that the transaction matches the amount and the address you asked for.
- You can withdraw free SOL only. SOL that open positions need stays in the wallet.
When something is wrong
- If the trading permission is removed, or its rules are missing, LP-Mimic pauses all trading on that account. To get trading back, email support.
- If the rules refuse three transactions in a row, LP-Mimic stops copying on that account. Closes still go on.
- When you add a wallet to copy, the console warns you if its address has the same first and last characters as a wallet the console already knows. This is a common trick to make you copy a fake address.
Error reports
When the console has an error in your browser, it can send an error report. Before the report is sent, addresses, keys, emails, quoted text and numbers in it are replaced with placeholders.What you should do
- Do not share your email code or your private key with anyone.
- Protect your email account. Anyone who can read your email can log in as you.
- Before you approve a withdrawal, check the first and last characters of the address.
- After you paste a deposit address, check its first and last groups.
- If you export your key, keep it offline and secret. Anyone who has it can move the funds.
- Send only SOL to your wallet.