← DashboardDuckFacts ↗
Project identity · manual review

Verify your app

Share a few details and proof of your project. You can connect a builder code or submit a standalone app profile without one.

What happens next

1Your request and proof image are sent for manual review.

2I check the attribution or project details and public links.

3Approved apps get a verified profile on DuckFacts.

Project informationRequired fields *

Use this when your app has Base builder-code attribution. It keeps your WTU, transactions and rank connected to the verified profile.

Base docs ↗

The code used in your Base transactions, for example bc_mwa18m77. Learn how builder codes work ↗

Choose the category that best describes the app. I may adjust it during manual review.

Optional, but recommended for future ownership verification and wallet-based features.

PNG / JPG / WEBP · max 1 MB
Selected app logo preview

If you do not upload a logo, the dashboard will use your website favicon after approval.

PNG / JPG / WEBP · max 5 MB
Selected project proof screenshot preview

Please show the builder code inside your app settings. Open the example below if you need a reference. Do not upload private keys or secrets.

View example screenshotBuilder code visible

Show the code in context

A settings screen is ideal: the app name and builder code should be visible together.

Example of a project settings page showing Celebration Hub and builder code bc_mwa18m77

This image is an example only. Upload your own screenshot from your project settings.

App names, websites, and social links are added manually. Basic checks are performed, but mistakes are always possible. DYOR before interacting with any app, website, wallet, or contract.