Private keys management for smart contracts deployment

1 point

4 years ago

A big problem with the current frameworks (like Hardhat or Truffle) is that you end up putting your private keys in a `.env` file. Despite the risk that you commit it by mistake, the keys are in cleartext on your computer. That is bad. A few months ago I developed a solution for it

https://github.com/secrez/cryptoenv

CryptoEnv allows people to encrypt their private keys in `.env` files and manage the entire process in full security.

My team at Mobland is using it in production since then and it is working great. I wonder if someone out there is using it, what do you think about it and if there are suggestions for improvements.

Thanks.