How to prevent having to `personal.unlockAccount()` all the time when using `geth` and `Remix`?

Question

How to prevent having to personal.unlockAccount() all the time when using geth and Remix?

I'm using geth and Remix in combination to learn contract development.

All the time, I've to switch to the terminal and enter personal.unlockAccount() to use Remix.

Is there an option to unlock the account on a permanent basis when testing things?

Answer 1

you can specify the unlock duration in unlockAccount:

personal.unlockAccount(addr, passwd, duration)

Unlock the account with the given address, password and an optional duration (in seconds).

so use for example ; personal.unlockAccount(addr, passwd, 300) //unlock for 5 minutes

web3.personal.unlockAccount(addr, passwd, 0);// the account is unlocked untill geth stops running.

Answer 2

Remix allows you to switch to a JavaScript VM (like TestRPC) that has an account with a lot of Ether and several unlocked accounts - and very quick block times. It is very helpful for learning Solidity and quick development iterations:

Answer 3

Use any one of the below options

1. testrpc -u Account#
2. testrpc --secure
3. web3.personal.unlockAccount("address", "pass", 0);
4. geth --unlock YOUR_ACCOUNT_ADDRESS --password YOUR_PASSWORD