And then we can proceed to load, and add each users' password whenever a user sends the
create_password HandleMsg. Note that I'm assuming we would generate the
&[u8] key for the hashmap from the user's wallet address. This approach has a huge problem! That is whenever we want to add another wallet's password to the hashmap, we must load the entire hashmap with all the passwords stored inside it. This will increase gas costs as we gain thousands of users. Moreover, loading the hashmap for queries will strain the node.