0.12.0 shows negative balance.

[Laviathon]

After I find a block 0.12.0 is showing a negative balance until confirmed.  I need this to just be unconfirmed,  not negative.

Any Clue?

[1714895263]

1714895263

[--Encrypted--]

After I find a block 0.12.0 is showing a negative balance until confirmed.  I need this to just be unconfirmed,  not negative.

Any Clue?

back up your wallet first.

start qt with -rescan commands. if there's an already double spended transaction in your wallet then start with -zapwallettxes, quit, start again with -rescan.

edit:
wait. what do you mean by finding a block? as in syncing?

[Laviathon]

back up your wallet first.

start qt with -rescan commands. if there's an already double spended transaction in your wallet then start with -zapwallettxes, quit, start again with -rescan.

edit:
wait. what do you mean by finding a block? as in syncing?

No dice against the first part and no, not syncing, finding a block.

https://blockchain.info/block/000000000000000000a330db360854ad4c3aa4694be60ae482f2a0218ded8ef4

My payouts from previous blocks fail because the wallet is showing a -25 BTC balance from the new block.

[achow101]

No dice against the first part and no, not syncing, finding a block.

https://blockchain.info/block/000000000000000000a330db360854ad4c3aa4694be60ae482f2a0218ded8ef4

My payouts from previous blocks fail because the wallet is showing a -25 BTC balance from the new block.

Hm, that is strange. Can you provide the debug.log? Do you think you can reproduce this error (on testnet or regtest because it is easier to find blocks there)?

[Laviathon]

Never mind.  Figured it out.  I'm an idiot and had front end set wrong.

[shorena]

Never mind.  Figured it out.  I'm an idiot and had front end set wrong.

Wana share the solution? Others might have a similar problem in the future. I suspect you had to wait 120 confirmations for the block to mature, but Im not sure if thats what you mean with "front end set wrong".