We built an LP copy trading layer on top of Uniswap v4 on Robinhood Chain.
The idea was simple: find people who LP well and copy their positions automatically.
To make that useful, we built our own analytics engine. It turns onchain pool and position events into analytics: PnL, ROI, win rate, profit factor, fees and holding time.
Start with a pool and explore its LPers, or filter wallets directly. Check their trades and price charts, choose your donors, then set your entry size, budget and exit rules.
Copypaste handles the copying. You decide who to follow and how to trade.
Built on open infrastructure. Our analytics and automation on top.
https://t.co/3jJuoAQLk6 - invite only.
@Uniswap@RobinhoodCrypto
market’s cooled off a bit, but wide-range spot LP on Robinhood Chain is still dripping fees. pocket money, basically.
robinhood:0xedbf91223639800bcd5756815caf908df3b890be / $USDG · robinhood:0x18e674231a58c239dc7daedcffe15ec3a24cff5c / $USDG
The pool locked the exit. We built another one.
Yesterday, LPs in $GC / $USDG on Robinhood Chain could add liquidity, but withdrawals failed because the $GC contract blocked the token transfer.
Copypaste now flags pools like this with LP exit risk and skips new entries. The filter is already on for all Robinhood Chain accounts.
Already in? If $USDG can still be recovered, Close offers an emergency exit. You confirm, take the $USDG, and leave the $GC behind.
What if your LP copy bot followed a scammer straight into their pool?
@betmoardotfun breaks down how copy trading bots on @Polymarket lost at least $75K by treating fake pending trades as real fills.
On Robinhood Chain, there’s a version of that trap for LP copy trading.
An attacker sets up a scam token or liquidity pool, opens a position on @Uniswap v4, and mints the LP NFT to a wallet that copy bots follow. The NFT is real. The transaction is confirmed. And the donor never opened the position.
A bot that only watches NFT ownership sees a fresh LP entry and copies it. Now real money is flowing into the attacker’s pool.
We shipped Verify donor sender in Copypaste to block that signal before a copy is queued. If the opening transaction came from another wallet, we skip it. It’s on by default on Robinhood Chain (@RobinhoodApp), with no extra RPC calls.
Safety Filters also let you set minimums for pool TVL, volume, token market cap, and holder count before copying.
The question to ask before copying an LP position: who actually opened it?
At least $75K was lost by copytrading bots today by an exploit from malicious actors
This is how it works and how we protect you from this on betmoar 👇
Big all-time PnL. But who’s actually trading well this week?
Added timeframes to Donors in Copypaste.
Choose 24H or 7D and filter by PnL, win rate or closed positions to find LPers who were active and profitable during that window.
Then dig into their wallet analytics and position history, pick a donor and set up LP copy trading with your own sizes and limits.
@Uniswap v4 liquidity pools on @RobinhoodApp’s Robinhood Chain.
Choose your timeframe before you pick your donor.
Night shift on Robinhood Chain: $VRAX LP 👇
An overnight dip. A morning recovery. Swap fees along the way.
$2,600 entry → +$102.97 net PnL (+3.96%) in 8h 58m.
$103.91 in LP fees.
Choose your donor and limits. Copypaste handles the copying.
GM, democrats 🫏
They’re counting votes. We’re adding liquidity.
Sizing up our Uniswap v4 LP positions on Robinhood Chain today. Have a good workday, everyone — let the pools clock in too.
Still waiting for that 2–3x token runner before Friday. If our donor catches the entry, I want Copypaste copying it while I’m busy.
One useful detail: you don’t have to copy everything a donor does. Your filters decide which LP entries qualify. Your settings control entry size, budget and position limits.
Find the LPers through pool and wallet analytics. Copy their positions. Track the fees and PnL.
Donors hunt. Copypaste handles the copying. I get some work done.
Your trading server gets hacked.
What can the attacker actually sign?
That’s the security question worth asking before users deposit funds.
1. Lock down the server.
Disable direct root SSH and password logins. Run services with limited permissions. Use a default-deny firewall — UFW or nftables — and expose only the ports you need. Keep databases and admin tools off the public internet.
2. Isolate the signing keys.
Keep raw wallet keys out of the app server. One approach: AWS Nitro Enclaves with KMS. Store encrypted key material, and let KMS release decryption material only to the approved, attested enclave.
A compromised host shouldn’t be able to read the signing key.
3. Restrict what can be signed.
An isolated signer still needs rules: allowed contracts, recipients, amounts and transaction methods. Check the actual contract arguments, including where the funds end up.
Keep permission to change those rules separate from the trading server. Otherwise, an attacker can simply rewrite them.
4. Protect wallet access with MFA.
With embedded wallets such as Privy, configure wallet-level MFA for sensitive user actions, including withdrawals and key exports. Prefer passkeys; authenticator apps such as Google Authenticator are another option.
Give automated trading narrowly scoped permissions, without unrestricted withdrawal authority.
5. Assume the front end can be replaced.
A disabled button is not a security boundary. Enforce permissions at the signer, wallet provider or contract, and verify the real amount and destination in a trusted confirmation flow. Authenticator codes can still be phished.
One distinction matters: wallet MFA protects access through the provider. It cannot rescue an ordinary wallet after its raw private key has been stolen — that key can sign outside the app.
Build for the day one layer fails.
What happens to an LP copy trade while you sleep?
Here’s one $WORM / $USDG position our software managed overnight on Uniswap v4, Robinhood Chain.
It started above the LP range, earning no fees. When the price entered the range, it began collecting swap fees.
The price then dropped further. Fees kept accumulating, and a late rebound helped the position close at +2.88% net PnL after 1d 34m.
One useful thing about Copypaste: copying a donor doesn’t mean giving up your own rules. You choose who to follow, set your position size and limits, and can set exit rules independently of the donor.
Copypaste handles the positions while you’re away. You can review the price history, LP range, fees and PnL afterward.
@Uniswap@RobinhoodCrypto
We built an LP copy trading layer on top of Uniswap v4 on Robinhood Chain.
The idea was simple: find people who LP well and copy their positions automatically.
To make that useful, we built our own analytics engine. It turns onchain pool and position events into analytics: PnL, ROI, win rate, profit factor, fees and holding time.
Start with a pool and explore its LPers, or filter wallets directly. Check their trades and price charts, choose your donors, then set your entry size, budget and exit rules.
Copypaste handles the copying. You decide who to follow and how to trade.
Built on open infrastructure. Our analytics and automation on top.
https://t.co/3jJuoAQLk6 - invite only.
@Uniswap@RobinhoodCrypto
Slow cook LP on Robinhood Chain 🍲
A wide liquidity range, a longer hold, and swap fees adding up little by little on a quieter token.
This $microduck / $USDG position ran for 15h 7m and closed at +1.81% net PnL. Fees are already included.
LP copy trading in https://t.co/3jJuoARj9E — choose your donors, set your size and limits, and let the software manage the positions.