Felix Lange a9f26dcd0d 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.		2016-04-12 15:58:07 +02:00
..
keystore	accounts: cache key addresses	2016-04-12 15:58:07 +02:00
v1/cb61d5a9c4896fb9658090b597ef0e7be6f7b67e	accounts, crypto: move keystore to package accounts	2016-04-12 15:56:49 +02:00
v1_test_vector.json	accounts, crypto: move keystore to package accounts	2016-04-12 15:56:49 +02:00
v3_test_vector.json	accounts, crypto: move keystore to package accounts	2016-04-12 15:56:49 +02:00
very-light-scrypt.json	accounts: cache key addresses	2016-04-12 15:58:07 +02:00