Verify Quickscope: Permissions and Execution
Understand account permissions, deployment records and the evidence needed to measure a copied trade.
Updated September 6, 2026 · Quickscope Team
Quickscope's ownership model and its trading outcomes are separate things to verify. An owner-only withdrawal function does not prevent losses from trades, malicious tokens, low liquidity or software faults.
Owner permissions and operator permissions
The account implementation restricts withdrawal, operator replacement, account caps and pausing to the owner. The operator can submit supported trading plans through validated venues. Plans can contain swaps and supported buy or sell operations; the permission is broader than a simple buy button.
The contract checks account-level USDG spend limits and the minimum output encoded in a submitted plan. The service separately uses per-trader budgets, sizing and slippage settings. Do not assume every value in the copy form is independently enforced on-chain against a compromised operator.
A compromised operator can still trade badly or churn assets through supported pools. Withdrawal control does not guarantee preservation of value. Verify your account's owner, operator, caps and implementation before funding it.
Deployment records
The project's deployment record dated September 4, 2026 lists these addresses on Robinhood Chain, chain ID 4663. They are reference addresses, not deposit destinations. Your own smart account has a separate address.
- CopyExecutor implementation: 0xc6AF5245433F72E7261012617034f62359b8ADc8
- CopycatFactory: 0xD95515e6a164506Ca7c1115b83f886c42B014ac5
- FeeVault: 0x98e405b39678FAb14b631bAAAC75F2FbdE8f5da0
- USDG token: 0x5fc5360D0400a0Fd4f2af552ADD042D716F1d168
Check chain data and your actual account configuration before relying on these records. Listing an address is not evidence of a third-party audit or explorer source verification; this page does not claim either.
Measure four stages, not one speed number
- Detection: when the service observes source activity.
- Preparation: when an eligible copy plan is ready to submit.
- Submission: when the copy transaction is broadcast.
- Confirmation: when the copy has actually executed on-chain.
Earlier site copy referenced a roughly 2.7-second preparation measurement. A public sample set and reproducible report are not provided here, so that number should not be treated as a verified performance benchmark or a fill-time promise. Quickscope does not guarantee execution before the source trader.
How to compare a source trade with a copy
Record both transaction hashes, chain IDs, token addresses, token amounts, fees and confirmation times. Calculate the effective entry price from actual amounts, rather than from a quoted price or a screen notification. Distinguish block timestamps from local observation timestamps; they can have different precision.
For a useful aggregate report, specify the date range, sample count and eligible population, then include skipped and failed copies as well as successful ones. Report median and tail latency separately. A handful of successful fills does not establish typical performance.
Stopping copies and withdrawing
Stopping a subscription does not liquidate tokens already held. Owner-only withdrawals remain contract operations even if the website is unavailable, but require the owner's wallet, network access and transaction fees. Withdrawing a token is not the same as selling it.
Read the FOMO setup guide and security explanation before starting.