I was thinking about that and I remembered that we wrote about these thing later:
1. have PoDC only wallet unlock option
2. auto setgenerate true 1 on PoDC (maybe both can be cumulated in 1 command or settings option)
3. and those different icons for different tx
I like #2 and #3, but on #1, I dont really like the way the POS coins implement that checkbox.
The problem with the implementation is it gives the user a false sense of security (when there is none).
If we add the option to unlock for staking only, then the user thinks their funds are secure (just because *they* cant spend them).
But in reality the whole point of making an encrypted wallet is to keep a hacker from stealing it.
So what you have in that case is someone moving 2 million biblepay to the controller , encrypting the wallet, clicking "unlock for staking only" and thinking they are secure. Then when they get hacked, the hacker sends the whole 2 million out.
Otoh, when we just leave it the way it is, the user is forced to store the 2million in a cold wallet and leave only 50K on the controller. OR manually take the risk and unlock the wallet. This is far better , the way it is, imo.
I have not been able to think of a better solution to this. It is possible to pull a hash from somewhere any make biblepay unlock the wallet, send the podc, and lock the wallet, but where is it going to pull the hash from if it does not open up a hole for a hacker to be able to see the file to find the hash? Its not an easy issue to solve.