Share feedback and ideas
Read public feedback, add context to an existing idea or propose something new.
TL;DR
- Search public feedback before creating a duplicate idea.
- Explain the outcome you need and why it matters.
- Use private Support instead when the report contains account-specific details.
Public Feedback helps people see, discuss and add context to product ideas. It is not the right place for wallet details, account identifiers or a private support investigation.
Search before creating an idea
Browse public feedback and ideas for an existing post that describes the same outcome. Add distinct evidence or a use case there when it moves the idea forward.
If the outcome is genuinely different, share it with the composer at the top of the public feedback board.
Explain the outcome, not only the feature
Describe the situation, the result you expected and why that change would help. Include enough context for another person to recognise the need without publishing personal account information.
Keep private issues private
Move a problem involving your account, wallet or non-public evidence to private Support. A public post cannot provide a safe investigation channel.
Public means visible to others
Keep recovery phrases, private keys, contact details and account-specific screenshots out of Feedback. Redact private information before attaching any example.
Common questions
What if somebody has already posted my idea?
Add the different outcome or use case to the existing public feedback instead of creating a duplicate. New context is more useful than another title for the same request.
Which route should I use for a bug tied to my account?
Use private Support. Describe the expected and actual result there, and keep recovery material out of every message.
How can I tell whether the idea has already shipped?
Check the platform changelog, then compare the current tutorial or live interface with the outcome you need.