For users don't want to set/manage a passphrase a default passphrase
"passphrase" will be used during wallet creation.
At startup, the wallet tries to unlock itself using the default
passphrase, or a user provided one (using -p).
Users that prefer a passphrase can override the default one at wallet
creation time using -p, or use the walletpassphrase rpc when
the wallet is running. This will prevent the wallet from auto-unlock,
and preserve the lock-by-default behavior.
1. remove lbcdusername and lbcdpassword
2. rename (username, password) to (rpcuser, rpcpass)
Most users are confused with the lbcduser and username at first,
and choose to use the same credentials between lbcd and lbcwallet.
1. Remove passphrase support for public keys.
2. Rename privPassphrase to passphrase to avoid confusion.
Note:
There has been a bug in the prompt, which prevents users from
specifying a custom public passphrase. So, most wallet databases
have been using the default password for the public keys, anyway.
