Skip to main content


What is the dApp Store Kit?

dApp Stores built by anyone, for anyone: The dApp Store Kit allows anyone to build a dApp store, where they can list any/every Polygon as well as EVM dApp, set their own rules for monetization/distribution/curation/governance, brand it as they see fit, and more. It solves the problem of Web3 dApp Discovery, and also makes a compelling use case for dApps against centralized app stores by Apple and Google. The stack will focus on mobile and solve a key problem of the lack of mobile Web3 app discovery.

What is the difference between the dApp Store Kit, dApp stores, and dApp?

  • dApp Store Kit: A open-source framework with a set of tools and standards that will help developers in building out their own dApp stores
  • dApp stores: These are the storefronts that will be built on top of the open-source layer and will be accessible to the end-user
  • dApps: These are the decentralized applications that will be part of the different dApp stores

Who will pay the gas fees to publish the dApps onto the registry?

The registry is entirely on-chain and the gas fees will be paid by the dApp developers to publish the dApp.

Would the dApp Store Kit support both Android and iOS?

We are starting off with Android since it covers more than 70% of the user base and eventually plan to move on to iOS once the regulations start getting relaxed

Can users modify the files in the registry directly on GitHub?

Yes, the user can directly raise a PR from Git.

Who moderates requests to add, delete and modify?

Meroku DAO (Community Partner) is moderating at the moment, but post the on-chain migration, it will be managed by a group of community members.

Can you explain the wallet experience? Is the Web3 context injection a part of this?

The dApp Stores will be able to connect to any mobile wallet app. Then for any web-based dApp that will be invoked inside a web view in the store, the web3 context can be injected from the dApp Store directly without the need for going out of the store

Where do we see these dApp stores living/being hosted?

The dApp stores will be hosted by the store developers themselves. They are free to choose the domain or platform on which they deploy these storefronts

If it is not an Android app (say PWA), whether the Android policy changes will be applicable?

If it's a PWA, it will be invoked in the dAppStore as a website inside the android webview, so it wouldn't matter

Will Android policy changes be a blocker for HTC DS?

Here, if the developer is having Google Play's billing system for IAP then the 15%-30% service fee will count. They will have to move away from this and implement a 3rd party IAP or have crypto payments. As of now HTC doesn't have any App Store and hence no API/SDK that is required to be integrated into apps specific to HTC. So, shouldn't be a blocker.

How to avoid / identify duplicate Dapp in the DSK?

Every developer registering their dApp will have to go through a domain verification process. This is a one time process and cannot be done by a 3rd party other than the dApp developer itself

Since the dApp registry will be maintained onchain, will that prohibit any dApp to be loaded on registry? (e.g. CoinGecko, do not have any touch-point onchain)

No, it won't! As only the dApp details are stored on-chain like an NFT's and dApps that doesn't have web3 elements like data aggregators, analytics platforms, etc. can also be part of it.

Are you guys launching an app yourselves or will this dappstore show up in wallets?

Dappstores built using the DSK can reside anywhere. We are just providing tools at an infra level and don’t control how the front-end implementation looks. You can build your dappstore however you want and launch it wherever you want.

For authorization and authentication would we need to adopt the protocol spec and therefore just our android apk won't suffice

Anything can work. If you have an existing social or a mobile number login, that also works.

How would we go about updating our app, do we send the APK every time?

You have to upload the latest build and update the version and metadata too.

What will be the PR acceptance process for a dApp to be added to registry?

If every detail is filled, then the PR is directly approved after review.