Blox Social Trading Revisited: Copying Positions Is Not Due Diligence
Blox and its CDT-era narrative combined portfolio tools with social investing. Learn how to verify current status and why copied trades carry independent risk.
This guide separates the working mechanism from marketing claims and shows what a user, developer or buyer must verify before relying on it.
Key takeaways
A social graph can reveal ideas; it cannot transfer another trader’s timing, liquidity or risk tolerance.
Historical CDT features and partnerships must be verified before being described as current.
How it works
A social trading platform connects accounts or wallets, displays performance and may automate replication. The follower receives their own fills after latency, fees and slippage, so results can differ materially from the leader’s chart.
Where the risk sits
Custodial access, exchange API keys, selective performance history and conflicts from referral or token incentives can distort results. A leader may also change strategy after followers commit capital.
What to verify
Confirm the legal operator, live applications, current token role, read-only versus trading permissions, withdrawal controls, full drawdown history and whether deleted or losing accounts remain in statistics.
Decision checklist
Use current primary documentation, exact contracts or legal entities, administrator permissions, fees, liquidity and the complete exit path. Test a small transaction and record what happens when an interface, oracle, operator, bridge or counterparty fails.
Keep a dated baseline of addresses, reserves, governance roles and normal withdrawal results. Define an observable stop condition before increasing exposure and retain enough native gas and independent wallet access to act without customer support.