Skip to content
  • Felix Lange's avatar
    a9f26dcd
    accounts: cache key addresses · a9f26dcd
    Felix Lange authored
    In order to avoid disk thrashing for Accounts and HasAccount,
    address->key file mappings are now cached in memory. This makes it no
    longer necessary to keep the key address in the file name. The address
    of each key is derived from file content instead.
    
    There are minor user-visible changes:
    
    - "geth account list" now reports key file paths alongside the address.
    - If multiple keys are present for an address, unlocking by address is
      not possible. Users are directed to remove the duplicate files
      instead. Unlocking by index is still possible.
    - Key files are overwritten written in place when updating the password.
    a9f26dcd
    accounts: cache key addresses
    Felix Lange authored
    In order to avoid disk thrashing for Accounts and HasAccount,
    address->key file mappings are now cached in memory. This makes it no
    longer necessary to keep the key address in the file name. The address
    of each key is derived from file content instead.
    
    There are minor user-visible changes:
    
    - "geth account list" now reports key file paths alongside the address.
    - If multiple keys are present for an address, unlocking by address is
      not possible. Users are directed to remove the duplicate files
      instead. Unlocking by index is still possible.
    - Key files are overwritten written in place when updating the password.
Loading