[bisq-network/bisq] DAO: Submitting a proposal (2 BSQ burnt) labels entire UTXO "unverified" until block is processed, preventing submission of other proposals (#2107)

[BravoIndia]

See below:

![used 2 bsq for vote](https://user-images.githubusercontent.com/33473721/49790327-7d8ed300-fd60-11e8-90eb-3478855bb50b.PNG)


I had 9998 BSQ and burnt 2 to submit the proposal, causing 9996 to be "unverified" until the block was processed.

Since my entire BSQ balance is one UTXO that got spent as an input in a proposal request 
(tx: https://explorer.bisq.network/testnet/tx.html?tx=f86258a7ddfbfba163eaa54855ec400342f5e1d51dbedc93205f5e4b34ecff3c),
the remainder (9996) became "unverified" in the DAO gui, preventing other proposal-making until the next block.

![warning](https://user-images.githubusercontent.com/33473721/49790362-98614780-fd60-11e8-8929-3afe61ba3977.PNG)

Should Bisq be able to recognize the output address is controlled by the same wallet?

Perhaps this is working as intended/there is no workaround, in which case perhaps the warning notice should be updated to make the users aware they simply must wait for the next block? Maybe with a link to the explorer? In general perhaps it makes sense to provide the transaction hash for a proposal made in the confirmation notice.

Thank you

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/issues/2107
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20181211/0cef6882/attachment.html>