Release types and requirements

Estimated reading time: 3 minutes

Sections in this page

• Developer mode releases and public release
• Release Requirements
  • 1 - General information
  • 2 - Security
  • 3 - Embedded app
  • 4 - Companion Wallet
  • 5- Documentation
  • 6 - Support
  • 7 - Marketing (Mandatory for Public release)
  • 8 - Warranty and liability
• Disclaimer

Developer mode releases and public release

There are different release types for an application:

• Developer mode release
• Public release (official Ledger support)

An application can go through Ledger acceptance several times, according to release type.

  Note
Until the application is audited, the message Pending Ledger Review is displayed when the application is used. The user must acknowledge this warning by pressing both buttons to use the application, which is at their own risk.

Developer mode applications are considered experimental and such application will be visible only when the developer mode setting is enabled in Ledger Live settings.

  Note
Some applications are only visible if developer mode is enabled, not because of a lack of security review, but rather because they are considered too complex to use. For example, the mandatory compatible GUI may be missing, or perhaps the application is considered too technical for the majority of users.

Release Requirements

1 - General information

• Embedded app name
• The name of your token as displayed in CoinMarketCap
• Legal Entity name
• Postal address
• Email address

2 - Security

• I have read the security guidelines
• The guideline_enforcer workflow succeeds
• All vulnerabilities have been fixed

3 - Embedded app

• I have read the coding guidelines
• Embedded app source code (GitHub repository)
• My app repository has a test folder that contains the Functional tests and Unit tests
• The App has been fully tested with a companion wallet (CLI or GUI)
• Two icons for the Ledger Stax, Nano and for the Ledger Live Manager in PNG or GIF (see Icons)
• Video of your application running on the Ledger device (for Ledger Nano only)
• The App has a Blind Signing setting (if applicable)
• The Guidelines_enforcer and Build_and_functional_tests workflow succeeds

4 - Companion Wallet

• A link to the Companion Wallet The wallet must give an option to verify the receiving address on a Ledger device. It should also have an affiliate link next to the “Connect with Ledger” option. You must provide either:
  • a link to the CLI repository, or
  • a link to the GUI running on Windows/MacOS/Linux (mandatory for Public release)

5- Documentation

• Document in the App’s repository the list of the app’s APDUs and status words
• Link to a Google doc tutorial about how to install and use your app (see Third Party Applications Support)
  • The doc must include the link to the published tutorial hosted on third party website

6 - Support

• I have read the support page
• Main support contact (mail address, Slack/Reddit/Telegram/Discord communities)

7 - Marketing (Mandatory for Public release)

• I have read the marketing page
• Marketing plan

8 - Warranty and liability

• I have read and agree with information laid out the warranty and liability disclaimer

Disclaimer

Ledger’s release of a third party application must not be considered as any form of partnership or endorsement.

---

Did you find this page helpful?

How would you improve this page for developers?

I am a developer.
Contributors will be chosen randomly to receive rewards. Check this box to send your email and participate.

Ledger collects your email address to send you rewards for your contribution to improve the Developer Portal documentation. Learn more about how we manage your data and your rights.

By providing your email address, you consent that Ledger may contact you for rewards delivery purposes. If you are part of the randomly selected contributors, we will send you an email to ask for your physical address and if necessary, ask you for additional information on the suggestion you made. Your information will only be available to Ledger and will be retained for no longer than 90 days. It may be transferred to non-European countries that ensure an adequate level of protection or under the standard contractual clauses adopted by the EU Commission.

Please note that you may withdraw your consent at any time, access your data and request their rectification or deletion. You may also request the limitation of the processing of your data. To exercise your rights or for any question on the processing of your data, please contact LEDGER’s Data Protection Officer here. If nevertheless you believe LEDGER did not adequately address your concerns and mishandled your data, you may lodge a complaint with the personal data protection authority of your country.

External Development

← Previous

Security Audits

Next →