1. Official Links
Purpose | URL | Notes |
Web app | Always verify the TLS lock and ares.pro domain before signing anything. | |
Waitlist | Submit your email to request access. | |
Invite redemption | Each code is single-use. Keep the tab open until onboarding finishes. | |
Documentation | (this help center) |
|
Status (network) | There is no dedicated Ares status page yet; check Solana first. |
There are no other official domains (no .trade, .xyz, etc.). Report imposters to support@ares.pro.
2. Community & Social
Channel | Link | When to use it |
Discord | #announcements for releases, #help for product questions, #bug-reports for reproducible issues, #suggestions for feature requests. Team members are tagged with the Ares role. | |
Telegram (community) | Quick mobile-friendly chats and broadcast alerts. Official admins are listed in the channel header. | |
X / Twitter | High-level updates, new feature teasers, and competitions. DMs are closed; use Discord or email for support. |
Keep all conversations inside these channels. Team members will never DM you first asking for a seed phrase or invite payment.
3. Product Resources
Getting Started – Complete onboarding checklist (invite → wallets → first trade).
Web App Guide – Detailed tour of Horizon, wallet tools, TG tracking, rewards, and settings.
FAQ – Quick answers (fees, supported DEXs, troubleshooting).
Meet Ares – Positioning, core pillars, and fee summary (share with prospective users).
4. Support Workflow
Self-check – skim the FAQ + Web App Guide for your issue.
Search Discord – many questions have already been answered in
#helpor#bug-reports.Collect context – for any escalation include:
Your Ares handle and registered email.
Wallet address(es) involved.
Transaction signature(s) or panel screenshots.
Timestamp (UTC) and timezone.
Steps to reproduce.
Open a ticket:
Preferred: post in
#help(product questions) or#bug-reports(reproducible issues) with the info above.Alternate: email
support@ares.pro(subject “Support –”).
During beta the team aims to reply within 24h on weekdays. Discord responses are typically fastest; email is best for long-form or private details.
5. Reporting Trading or Wallet Issues
Include the following so engineers can trace the event:
Data point | Why it matters |
Transaction signature | Lets the team inspect logs and on-chain errors. |
Wallet address(es) | Needed to query holdings and wallet-tracking feeds. |
Token contract / pool | Many issues are pool-specific (Raydium CLMM vs Pump.fun). |
Panel screenshot / preset settings | Shows the filters, Insta-Buy amount, and preset you used. |
Browser + OS | Helps rule out local caching or extension conflicts. |
Steps to reproduce | Speeds up QA verification. |
For transient Solana congestion (“Program failed”, “Blockhash not found”), try re-running with higher slippage/priority after checking status.solana.com. Only escalate if the problem persists or you see unexpected behavior (e.g., wrong fee, duplicated trades).
6. Feature Requests & Feedback
Discord
#suggestions: best place for idea threads, screenshots, and upvotes.Long-form feedback: email
support@ares.pro(subject “Feedback – ”). Include the use case, why it matters, and any comparable implementations you like.Public shout-outs: tag @arespro on X/Twitter for wins, memes, or release amplification.
Need something that is not covered here? Start in Discord #help with as much detail as you can share, then follow up via email if the conversation needs to move off-platform.