You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on triaging discussions around #1197, the aim is to introduce a feature that allows users to dynamically select wallet indices. It will allow users to manage multiple wallets within the predefined HD path.
The existing config system does not allow for the selection of different wallet indices within the same mnemonic derivation path. This limitation restricts users to a default wallet index, which can be inconvenient and limit those requiring access to multiple wallets derived from the same mnemonic.
Potential Implementation:
Config Enhancement: Extend Ignite's config system to include an option for specifying the account index. This could be a global setting or configurable on a per-account basis to accommodate different use cases.
Optional Flag: Include an optional parameter for the wallet index when generating accounts or performing operations that involve account derivation. This ensures that both manual and automated processes can leverage the dynamic wallet index selection feature.
Default Behavior: In the absence of a specified wallet index, Ignite should default to using the first wallet (index 0) to maintain backward compatibility and ensure that existing projects and configurations remain unaffected.
The text was updated successfully, but these errors were encountered:
Context:
Based on triaging discussions around #1197, the aim is to introduce a feature that allows users to dynamically select wallet indices. It will allow users to manage multiple wallets within the predefined HD path.
The existing config system does not allow for the selection of different wallet indices within the same mnemonic derivation path. This limitation restricts users to a default wallet index, which can be inconvenient and limit those requiring access to multiple wallets derived from the same mnemonic.
Potential Implementation:
The text was updated successfully, but these errors were encountered: