Functional requirements

Sections in this article

Guidelines on app name and ticker

Ensure that the application name defined in makefile matches the one you want to have displayed on the manager. Ticker name must be added via ledgerjs update and not directly on makefile.

Blind signing

For every transaction, the user must be able to verify on the device the amount being transferred and the destination address.

If the display of those parameters (Token, smart contract management) is not possible, the transaction should be rejected by the device unless the user has acknowledged blind signing such a transaction.

To implement this requirement it is recommended to have a setting menu with the possibility to enable/disable contract data.

You can find implementation example inside Ethereum, Solana or Elrond code base.

Wallet requirements

The wallet must give an option to verify the receiving address on the Nano device. It should also have an affiliate link next connect with ledger option

Smart contracts & token support

Ledger users must be able to verify every transaction they perform using your Bolos application. If your chain supports other tokens, ensure that the correct ticker, amount, and destination address are displayed while interacting with them. If this is not the case, you need to implement a blind signature setting on the application, which by default must be disabled.

Staking feature

For every staking operation, ledger users must be able to verify the amount, validator/nominator address(es)

Did you find this page helpful?

What would you like to see here?
Documentation requirements
Getting Started
Theme Features