Crypto//Keystore

- Legacy approach: each account stored as an individual encrypted JSON file in `/data/keystore`.

Legacy approach: each account stored as an individual encrypted JSON file in /data/keystore.

The node software (Geth) held the keys and signed transactions on behalf of the user.

Volume mapping (-v) was critical: keystore files must persist outside the container.

Now largely replaced by HD wallets — signing delegated to Metamask instead of the node.