Skip to main content
Good feedback explains what you were trying to do and what would have made the experience better. Search the portal first so you can vote or add detail to an existing post.

​
Choose the right type

  • Product Ideas: workflow improvements and feature requests.
  • Bugs & Broken Flows: errors, loading failures, and actions that do not work.
  • Data & Listing Corrections: inaccurate public entity data.
  • Trust & Verification: proof, claims, badges, or impersonation concerns.

​
Include

  1. A short outcome-focused title.
  2. The production page URL.
  3. What you expected and what happened.
  4. Steps to reproduce, browser/device, and approximate time for bugs.
  5. A redacted screenshot when it adds evidence.
Remove private keys, recovery phrases, passwords, session data, applicant information, and other private details before posting. Describe the outcome you need, not only the control you want. Explain who has the problem, how often it occurs, and what workaround exists. For trust or identity issues, use the dedicated reporting flow instead of a public idea post. Add only evidence you are allowed to share. Search existing feedback first. Add evidence or vote when the same problem already exists so discussion and status stay attached to one request.

​
Continue on dApp.ing

Open dApp.ing Feedback

Complete this task in the dApp.ing application.

Troubleshoot sign-in, account, loading, and save errors

Try a short recovery checklist, then report the details if the problem continues.

Report a listing correction

Report stale or incorrect listing information with a reliable source.
Last modified on July 24, 2026