Report a Bug

Something broke? Tell us in a way the team can reproduce — that's what makes the fix fast.

A bug report is most useful when it gives the team a clear path to repeat the issue. This page is a checklist for everything that helps — and the things that should never appear in a bug report no matter what.

Never include secrets

Seed phrases, private keys, wallet passwords, and one-time codes don't belong in any bug report — not even when support seems to need them.

Useful Details

Include as many of these as you can:

• Page or section — where the issue happened.

• Short description — one or two sentences summarizing what's wrong.

• Steps to reproduce — what you did before the issue appeared.

• Expected behaviour — what you thought would happen.

• Actual behaviour — what actually happened.

• Device type — phone, tablet, desktop.

• Browser or Telegram client — version when known.

• Relevant context — wallet address, transaction hash, token address, or order details (no secrets, see below).

A clear path to reproduce gets a fix faster than three paragraphs without one.

Account and Wallet Issues

For account or wallet bugs, add:

• Sign-in method used to access the account.

• Connected wallet type — Phantom, MetaMask, etc.

• Network — Solana, Ethereum, others as relevant.

• Wallet address if relevant to the issue (public address only).

• Exact error message when one appeared, copy-paste verbatim.

Never include:

• Seed phrases.

• Private keys.

• Wallet passwords.

• One-time codes / 2FA codes.

If a request seems to need any of those, it's not a legitimate request — stop and verify the channel through official support.

Trading Issues

For trading-related bugs:

• Token address or pair.

• Order type — Market / Limit.

• Amount.

• Time of the attempt — UTC if possible.

• Transaction hash when one was created.

• Trading Settings at the time — Slippage, Priority, Bribe.

If a transaction reached the blockchain, verify it in a block explorer first and include the transaction hash. The on-chain record is the ground truth.

Attachments

If the form supports file uploads:

• Attach only materials that help explain the issue.

• Remove private information before uploading — crop screenshots to avoid revealing balances, addresses, or other context you don't need to share.

• No videos longer than the bug actually requires.

More to Explore

Feedback

Non-urgent product input and suggestions.

Support Contacts

The right channel for direct help.

Help Center

The overview of every help-side option.

For urgent security issues — exposed seed phrase, suspected wallet compromise — move funds to a new wallet first. See Wallet Security Notes.

FAQs

How long until my bug is fixed?

Depends on severity and reproducibility. A clean reproduction path is the single biggest accelerator — vague reports always take longer than precise ones.

Should I screenshot the bug?

When it's visual or layout-related, yes. Strip sensitive info (wallet addresses, balances) that isn't relevant to the bug before uploading.

What's the difference between a bug report and feedback?

Bugs are things broken now. Feedback is everything else — suggestions, friction, requests, general comments. See [Feedback](feedback.md).

Why does the team need my Trading Settings?

Trade-related bugs often depend on the execution profile (Slippage, Priority, Bribe). Without those values, reproducing the bug is guesswork.

I can't reproduce the bug myself. Should I still report it?

Yes — describe what you remember and the conditions you were in. Even a partial report can correlate with other reports the team is tracking.