Meros uses BIP 39 mnemonics, which have a password. We support this functionality, and even have support for it in our RPC route. That said, these passwords can only be entered over the RPC. The wallet generated on boot doesn't have one.
This password is not requested on every TX (or after X amount of time), yet saved to RAM. That itself isn't necessarily a problem, except it's not saved to the DB either. This means anyone who loads a wallet with a password must use the RPC route every single time their node boots to ensure its usable.
This issue exists so we can plan how we want to utilize the password field and actually implement the design. It should be noted its okay to not keep the password in RAM (or the underlying private key), as we also support BIP 32 so we can save the HD pub key,
Meros uses BIP 39 mnemonics, which have a password. We support this functionality, and even have support for it in our RPC route. That said, these passwords can only be entered over the RPC. The wallet generated on boot doesn't have one.
This password is not requested on every TX (or after X amount of time), yet saved to RAM. That itself isn't necessarily a problem, except it's not saved to the DB either. This means anyone who loads a wallet with a password must use the RPC route every single time their node boots to ensure its usable.
This issue exists so we can plan how we want to utilize the password field and actually implement the design. It should be noted its okay to not keep the password in RAM (or the underlying private key), as we also support BIP 32 so we can save the HD pub key,