Skip to main content
This support guide helps you resolve common SeaBond issues faster. Before contacting support, check the steps below and prepare the details needed for investigation.

​
Check first

Before contacting support, confirm that:
  • you have reviewed the related docs and FAQ
  • your wallet is connected correctly and your network is working
  • the issue is not caused by short-term data syncing delay
  • your copy trading rule, funds, margin, and order status match what you expect
  • the issue still happens after refreshing the page or reconnecting your wallet
If the issue still exists, contact official support.

​
What to include

To help support investigate faster, include:
  • your UID or wallet address
  • the page where the issue happened
  • the approximate time of the issue
  • what you were trying to do, such as creating copy trading, closing copy trading, checking positions, or withdrawing
  • screenshots of the error message or page state
  • related order, copy trading rule, or trading record details
Avoid vague reports like “it does not work” or “there is an error.” More context helps support resolve the issue faster.

​
Use official channels only

Only contact support through channels shown on the SeaBond website, inside the product, or in official announcements. Official links:
SeaBond support will never ask for your seed phrase, private key, verification code, full API key, password, or remote control access. Do not trust anyone who asks for this information.

​
Who to contact

  • SeaBond page, data, copy trading, and account display issues: contact SeaBond support
  • Wallet connection, signing, or asset authorization issues: check your wallet and browser first, then contact your wallet provider if needed
  • Hyperliquid network, deposit, withdrawal, or on-chain trading issues: refer to Hyperliquid official docs and support channels
  • Third-party projects or external apps: contact that project?s own support channels

​
Response time

Support requests are handled based on the completeness of the report and the impact of the issue. Peak periods, weekends, or issues that require on-chain data checks may take longer.