PeekDrop сейчас в бета-версии.  Некоторые функции могут быть ограничены.

PD
PeekDrop .xyz

// AIRDROP_FEED.SYS / DETAIL.NODE

logo placeholder

Что такое Farside и как получить аирдроп: подробное руководство для новичков ◽

Upcoming

Farside — это некастодиальная платформа для автоматизированной торговли перпетуалами на Hyperliquid и dYdX. Их система баллов позволяет зарабатывать 1 балл за каждые $100 торгового объёма. Эти баллы определят будущее распределение токенов. В этом руководстве мы расскажем, как присоединиться и получить вознаграждение.

// AIRDROP_INFO
We need to output HTML fragment wrapped in
...
. Must follow all rules: use Tailwind classes, dark mode variants, proper typography, sections, lists, cards, alerts, steps, tables, etc. We need to parse the text and structure. We need to break into logical sections, use headings, maybe a card for key metrics, steps as step blocks, maybe a table for key metrics, maybe a list for steps, maybe a quote, maybe a callout. Let's outline: - Title: maybe H1 "Farside Airdrop Guide for Traders" (but original text doesn't have a title, but we can create a heading). Use H1 with appropriate class. - Intro paragraph. - Section: "What is Farside?" maybe H2. - Section: "Key Metrics" maybe a card with list. - Section: "How It Works" maybe description. - Section: "Step-by-Step Instructions" with steps as flex items (class "flex gap-4 p-4 bg-slate-50 dark:bg-slate-800/80 rounded-xl border border-slate-200 dark:border-slate-700 mb-4"). Each step: number in a div with class "flex-shrink-0 w-8 h-8 flex items-center justify-center bg-indigo-600 text-white font-bold rounded-full". Then description. - Section: "Important Notes" maybe a list or a note. - Section: "Editorial Tips" maybe a list. - Section: "Project Evaluation" maybe a card with scores. - Section: "FAQ" maybe a list or a series of
but we can use
    with questions and answers? Might be too complex. Use
      with list items each containing Q&A. - Maybe a quote block. - Maybe a callout for "Risks" with alert style. We need to ensure dark mode classes: for each element, background and text colors must have dark analog. Let's design:
      Inside: < H1 > maybe

      Farside Airdrop Guide for Traders

      Then intro paragraph:

      ...text...

      Then maybe a section "What is Farside?" with H2.

      What is Farside?

      ...text...

      Then maybe a card with key metrics:
      ... items ...
      But need to ensure dark mode: card background maybe "bg-slate-50 dark:bg-slate-950" and border "border-slate-200 dark:border-slate-700". Use "p-5 rounded-xl shadow-sm". Inside we can have list items. Let's create a card:

      Key Metrics

      • 🏆 Type of reward: Farside points → future token distribution
      • 🧮 Points system: 1 point per $100 traded
      • 🎁 Giveaway: 100 winners × 100 points = $10,000 worth
      • 🔗 Blockchain: Ethereum (MetaMask)
      • 🔄 Supported exchanges: Hyperliquid, dYdX
      • ✅ KYC: Not required
      But need to ensure dark mode for background and text: background is white (light) and dark: slate-900. Text is slate-700 (light) and dark: slate-300. Good. Next: Steps section. Use heading H2 "Step‑by‑Step Instructions". Then each step as a flex container. We need to wrap each step in a
      . Inside: number circle
      1
      then description

      ...text...

      . We have 8 steps. Let's list them. Step 1: Prepare wallet. Text: "Prepare your wallet. You’ll need an Ethereum‑compatible wallet (MetaMask, Rabby, or Trust Wallet). Ensure you have a small amount of ETH for gas fees." Step 2: Go to platform. "Visit the official Farside app (link via their X profile @farsideapp)." Step 3: Connect wallet. "Click ‘Connect Wallet’, choose your wallet, and confirm." Step 4: Start trading. "Select Hyperliquid or dYdX, set up your strategy with the grid bot or other automation tools. Every $100 of trading volume earns you 1 Farside point." Step 5: Earn points. "Points are tracked on the Trading Leaderboard; more points mean a larger future token allocation." Step 6: Optional giveaway participation. "To join the giveaway, complete tasks on the Alphabot page." Step 7: Check progress. "The leaderboard shows your points and ranking; monitor it regularly." Step 8: Wait for distribution. "The points system runs continuously; token distribution will be decided after the Token Generation Event (TGE). Stay tuned to official channels." Make sure each step description is concise. Now after steps, maybe a "Important Notes" section with a list or a note. We can use a
        with class "list-disc list-inside space-y-2". But maybe better to use a "note" with a border? Not required. Use a simple list.

        Important Notes

        • No deposits required – you can start with small amounts.
        • Gas fees (ETH) are needed for transactions.
        • Use the official Farside site to avoid scams.
        • KYC is not required, but verify official rules.
        • Points do not guarantee token conversion; treat the platform as a trading tool.
        Then "Editorial Tips" maybe a list.

        Editorial Tips

        • Use a separate wallet for airdrop activities for added security.
        • Start with small trades to test the platform.
        • Ignore rumors about extra rewards; rely only on official channels.
        • Follow @farsideapp on X for the latest updates.
        Then "Project Evaluation" maybe a card.

        Project Evaluation

        Trust Score: 70/100 – real product, supported by major exchanges, experienced team.

        Potential Score: 75/100 – strong utility, good integration, but tokenomics remain uncertain.

        Then "FAQ" maybe a list with Q&A.

        FAQ

        • How much can I earn? 1 point per $100 traded; also a giveaway of 100 winners × 100 points ($10,000 worth).
        • Can I use Trust Wallet? Yes, it’s EVM‑compatible; just ensure you have some ETH for gas.
        • What is a snapshot? A snapshot captures participants’ activity before the TGE; for Farside it will likely occur prior to the event.
        • Can I join if I start late? Yes, the points system is continuous – the more you trade, the more points you earn.
        Maybe a quote block:
        "Automated trading made simple – let the bot follow your strategy."
        Maybe an alert for risks:

        Risk of scams – always use the official Farside platform.

        Now we need to ensure all colors have dark analogs. Let's verify each class: - Article: bg-white dark:bg-slate-900 text-slate-800 dark:text-slate-300 (good) - H1: text-indigo-700 dark:text-indigo-400 (good) - Paragraph: text-slate-700 dark:text-slate-300 (good) - H2: text-slate-900 dark:text-white (good) - Card: bg-white dark:bg-slate-900 border-slate-200 dark:border-slate-700 (good) - List items: text-slate-700 dark:text-slate-300 (good) - Steps container: bg-slate-50 dark:bg-slate-800/80 border-slate-200 dark:border-slate-700 (good) - Number circle: bg-indigo-600 text-white (dark mode? Should have dark variant: maybe "dark:bg-indigo-700 dark:text-white"? But the rule says any background must have dark analog. The circle is a solid color; we need dark version. Since we are in dark mode, the circle should be darker. Use "bg-indigo-600 dark:bg-indigo-700". Also text-white remains white (maybe also dark:text-white). But we can keep text-white; it's okay because it's light on dark background. Ensure dark variant: "bg-indigo-600 dark:bg-indigo-700". Also maybe "dark:text-white" but white is already light; on dark background it's still fine. We'll include dark:text-white. - Step description: text-base md:text-lg text-slate-700 dark:text-slate-300 (good) - Important notes list: text-slate-700 dark:text-slate-300 (good) - Editorial tips list: same. - Project evaluation card: bg-white dark:bg-slate-900 border-slate-200 dark:border-slate-700 (good) - Trust score/potential: text-slate-700 dark:text-slate-300 (good) - FAQ list: same. - Quote block: border-l-4 border-indigo-500 pl-4 italic text-slate-600 dark:text-slate-400 (good) - Alert: bg-red-50 dark:bg-red-950/30 border-l-4 border-red-500 p-5 rounded-r-xl mb-6. Text: text-red-800 dark:text-red-300 (good) Check that we used any "dark:" for backgrounds: yes. Check that we didn't use any disallowed tags: we used
        ,

        ,

        ,

        ,

        ,
          ,
        • ,
          , (we used in FAQ). is allowed (not a document root). No