accounts: cache key addresses
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.
Showing
accounts/addrcache.go
0 → 100644
accounts/addrcache_test.go
0 → 100644
File moved
File moved
accounts/watch.go
0 → 100644
accounts/watch_fallback.go
0 → 100644
Please register or sign in to comment