Blockchain reorg causes problems

fireduck64 / jelectrum

An Electrum Server written in Java

MIT License

41 stars 15 forks source link

Blockchain reorg causes problems #9

Open SuBPaR42 opened 9 years ago

SuBPaR42 commented 9 years ago

2nd time witnessed...

Blockchain reorg at 372048 caused h.1209k.com to not advance and results in a "UTXO mismatch"

From 'electrum-server' logs...

[29/08/2015-11:05:41] blockchain reorg 372048 000000000000000003a23d5bdf78ebfc1a7a9bd0b2d1c47d20930f046febffa7 00000000000000000fc140b3bc958138fe1a7be3560d1b9a33be08c66f961aa4

fireduck64 commented 9 years ago

I think jelectrum is doing the right thing, except it might not be doing the block notifications to clients correctly. I think if a client disconnected or waited until the next block after the reorg, things would be fine.

However, I think a code change to detect more state changes in the block chain and advertise them appropriately would make sense.

SuBPaR42 commented 9 years ago

SO how do you "fix" it? Just restart the server and it announces it is on the correct block? Does the server get stuck or is it just a "advertisement" issue