Unlock requests show up as failed in the wallet

[jagerman]

Unlock requests that you send from your wallet show up as failed.

This happens, I suspect, because these txes have no outputs, nor fees, and so the wallet never recognizes the tx as one that it should care about: so it knows it produced the tx, but when it looks at txes that it should care about, the tx is not there.

Two options:

1. Make the wallet not care about unlocking: that is, it can submit them, but don't log them at all in the tx history. This is not so good.

2. Require that unlock txes have an output, and thus also a fee. Thus an unlock would now have 1-output back into the originating wallet, which would make the wallet see it.

3. same as 2, but also impose a configurable burn requirement to unlock so that you have to burn, say, 1 LOKI in order to initiate an unlock. (We could, at the same time, also add required burn fees to registration and staking).