I got a notification of a double spend in a block I voted on. I have never seen this before. Can anyone provide more info on exactly what happen with this block? Does this invalidate my vote ticket reward? Locked funds were returned. 2017-09-19 04:33:33.260 [INF] WLLT: Connecting block 00000000000000b88cb31d42740afad0df618fcdbcfd4643b1790b92db39679f, height 170014 2017-09-19 04:33:33.303 [INF] WLLT: Inserting unconfirmed transaction 63163f08a8bf3f836d17157d14d669806529e0ae3ea526c55d73902f8f357283 2017-09-19 04:33:33.356 [INF] WLLT: Voted on block 00000000000000b88cb31d42740afad0df618fcdbcfd4643b1790b92db39679f (height 170014) using ticket b1300251321d623b09f2e62a5981b7bda660ba73e22ff65e9a04ae44b9fdead3 (vote hash: 63163f08a8bf3f836d17157d14d669806529e0ae3ea526c55d73902f8f357283 bits: 1) 2017-09-19 04:33:33.585 [ERR] WLLT: Failed to process consensus server notification (name: `relevanttxaccepted`, detail: `unmined transaction cbd8583a44f109e3dd4e24df2bfc6aef6410ac8183e1272a625cc4aee8f2983e is a double spend of unmined transaction 63163f08a8bf3f836d17157d14d669806529e0ae3ea526c55d73902f8f357283`) 2017-09-19 04:40:21.839 [INF] WLLT: Connecting block 000000000000008dfdb8a087459e9389a4b79467e5246237965bb6711d2764d1, height 170015
Looks like you created two different votes. What does your voting setup look like? Are you using a stakepool or solo voting? This can be caused by two voting wallets both trying to vote with different voting preferences (votebits).
I am using a pool. I do have a local client set up as well. I recently upgraded to 1.0.8. I dont think I have set vote prefs on my local client. I have set vote prefs on pool so that may make sense. The pool says a vote was spent on block 170015. Nothing about 170014.
Then everything is working as expected. Set the voting preferences to match and it will create identical votes instead of different ones. Block 170014 is the block you voted on. 170015 is the block one of those votes was mined in.