A elastOS dApp store server is available to host your capsules and make them downloadable through the store capsule by all elastOS users.
The first time a capsule is published, or randomly after that, there is a manual review process from the Elastos team members, so your capsule won’t appear in the store capsule right after publishing it. Application updates are faster.
Note that this centralized process will change in the future and will be replaced with a decentralized community-based model.
Publishing your capsule requires to sign it using an Elastos DID. The Trinity CLI lets you create a DID this way:
$ trinity-cli did create
Save your DID string and mnemonics in a safe place. You will need to use them to publish your capsule, now but also every time you want to publish an updated version.
Your signature needs to be uploaded on the DID sidechain. You have to use the elastOS mobile application itself to scan the QR code provided during the DID creation, and pay a very low transaction fee to publish your DID on chain.
At first, your wallet app may have all ELA stored on the ELA mainchain, but nothing on the DID sidechain. You need to use the wallet capsule to transfer some amount to the DID sidechain (only the first time). A very small amount such as 0.1 ELA or less is enough to write several DID transactions.
You finally have to wait a few minutes for the transaction to be validated by the blockchain (first time only). After that, you will be able to upload your application. Awaiting your DID to be available on chain is required as the capsule store server looks for it while validating your published capsule.
Make sure to not store the created DID storage folder (in your current folder) to your GIT repository.
In case you cannot totally finalize the DID publication on chain, you can still retry to publish your created DID later using the following command:
$ trinity-cli did publish
$ trinity-cli publish --did did:elastos:yourdid --news "What's new information"