Currently, our Keyring type only allows adding new accounts sequentially, or more specifically, does not provide a standardized way to specify which index (or even derivation path) should be used to derive the next available account.
This is fine for our current hierarchical deterministic wallet mechanics as users are only allowed to derive sequential indexes, but presents a limit for hardware device interactions since:
- Users can preview the derivable accounts in a paginated manner
- Users can select specific indexes to derive, which are not required to be sequential
This limitation is currently worked around by clients, that interact directly with each keyring that is known to support specific methods to handle pagination and to set derivation path index, but it would be nice to have a standard way to support this (e.g. through new methods on the shared Keyring type or by creating a pagination helper wrapper)
We should propose a solution to this problem through an ADR.
Currently, our Keyring type only allows adding new accounts sequentially, or more specifically, does not provide a standardized way to specify which index (or even derivation path) should be used to derive the next available account.
This is fine for our current hierarchical deterministic wallet mechanics as users are only allowed to derive sequential indexes, but presents a limit for hardware device interactions since:
This limitation is currently worked around by clients, that interact directly with each keyring that is known to support specific methods to handle pagination and to set derivation path index, but it would be nice to have a standard way to support this (e.g. through new methods on the shared Keyring type or by creating a pagination helper wrapper)
We should propose a solution to this problem through an ADR.