TradeTok
Scroll. Watch. Copy. Trade.
About
The problem it solves 💡 The Problem TradeTok Solves DeFi trading is powerful but fragmented, complex, and intimidating: Finding credible trading strategies requires endless research across Twitter, Discord, Telegram, and forums. Copy-trading tools exist, but they’re often opaque, custodial, and centralized, requiring trust in a third party. Executing trades across chains is cumbersome — users must manually bridge, swap, and set parameters like slippage and stop-loss. Newcomers are left behind, while advanced traders struggle to monetize their strategies in a transparent way. ✅ The TradeTok Solution TradeTok makes social trading in DeFi simple, transparent, and safe: 🎥 Video-First Discovery — Creators share short, TikTok-style clips with their trade ideas, making strategies easier to understand than text threads. ⛓️ On-Chain Strategies — Strategies are published immutably via the StrategyRegistry contract, ensuring credibility and transparency. ⚡ 1-Click Copy Trading — Followers can instantly replicate trades with guardrails (slippage, limits, leverage caps) via the Zircuit Trading Engine. 🌉 Cross-Chain USDC Detection — Users don’t need to worry where their stablecoins are; TradeTok finds USDC across Base, Optimism, Arbitrum, and Mainnet. 🔒 Non-Custodial Safety — Users always keep control of their wallets; trades execute trustlessly with no middleman risk. 📊 Simple Portfolio View — Users can track ETH and USDC balances across chains with a clean, mobile-first dashboard. Smart Contract Address(es) Base Mainnet 0x8fd308C3F8596b5d4b563dc530DD84eBE69da656
How it's made
Challenges we ran into Building TradeTok wasn’t without hurdles. Some of the main challenges included: 🎬 Video-first UX in a mobile web app Getting a smooth, TikTok-style snap scroller with auto play/pause and tap-to-unmute in Next.js + React took fine-tuning for performance, especially on mobile. ⚖️ Cross-chain balance detection Detecting and aggregating USDC balances across Base, Optimism, Arbitrum, and Mainnet in a way that’s performant but not RPC-rate-limited was a challenge.