Basic Info

Update basic information about your .app

The following video provides a quick overview of how best to update your basic information. For more specific details follow:

Description of fields

Name

Name of your .app.

Description

Provide a detailed description of your .app. We recommend using 300 or more words to have good content.

URL

Your website is where people can learn more details about the .app.

Repo URL

If your project is Open Source, you may provide the repository URL of your .app. This is optional.

Contracts

Select the chains where your .app is available. We currently support Ethereum and EVM based chains. More chains will be added in the future.

Contracts Addresses

If your .app has a smart contract, ERC20, ERC721 or ERC1155 tokens, you should enter their addresses of them here. This adds another layer of trust to your .app.

Geo-Restrictions

To ensure your .app is distributed to the right audience legally, you must fill in the geo-restrictions. You can choose either whitelisted countries or blacklisted ones.

Anyone can access the .app metadata from anywhere since this information is present on the chain. Using this metadata, they may still be able to access your .app's URL and hence the .app itself. This field is used by .appStores using Meroku protocol to ensure they are distributing the right .apps to the right geography. You are advised to have appropriate steps at your .app level to ensure your .app is compliant with geo policies.

Category

Select from the categories in the dropdown.

Sub Category

Select the subcategories within a category from the dropdown.

If you want to suggest a category or subcategory to us, please use this form.

Language

Selecting the language will ensure your .app gets distributed to the right audience.

Minimum Age

This is the minimum age of the audience that should use your .app. This is used by app stores to ensure they are serving the right .apps to the appropriate audience.

Anyone can access the .app metadata from anywhere since this information is present on the chain. Using this metadata, they may still be able to access your .app's URL and hence the .app itself. This field is used by .appStores using Meroku protocol to ensure they are distributing the right apps to the right demographics. You are advised to have appropriate measures in place as well.

Tags

Tags that can be used to describe your .app.

Is Self Moderated

If your .app has some form of user action or user-generated content and you have appropriate measures to moderate the content, then select Yes. Otherwise, select No

Listed in Registry

Sometimes, you want to draft and save your .app metadata. Other times, you want to publish it live. This field will help you do it.

If you don't want to go live, keep this field unchecked.

If you plan to go live, you will need to check this field and set a date on which the .app should be go-live. By default, it is the current date.

Does your app use Wallet Connect?

This info is used by some of the .appStores. If your .app uses Wallet Connect you should select this and choose the appropriate version.

Note that WalletConnect 1.0 is being deprecated.

Saving Data

Once you fill in all the info, you need to click on the Save button. This stores the state in-browser. You will be able to store the data on-chain later.