Post
Topic
Board Announcements (Altcoins)
Re: [ANN][DCR] Decred - Hybrid PoW/PoS | btcsuite Devs | Tons of New Features | Go
by
bspus
on 03/03/2017, 21:24:20 UTC
Quote
08:35:04 2017-03-02 [INF] WLLT: Connecting block 00000000000006c0af1d5bc56213a056d2ab7a239bead873336e8f26691949a9, height 111891
08:37:40 2017-03-02 [INF] WLLT: Voted on block 000000000000091b2b16580ded143bbb8e7fe224f868d6f87b44b00723676c97 (height 111892) using ticket bf87c95d568baa86a22b2d9b0338f903a98277968333911b0ff197e750301103 (vote hash: e7fa0202e8f8ccec0e6865ac77ec1cbe337c5aa7fc1e6335a0b763cb5b7856b3)
08:37:40 2017-03-02 [INF] WLLT: Connecting block 000000000000091b2b16580ded143bbb8e7fe224f868d6f87b44b00723676c97, height 111892
08:43:19 2017-03-02 [INF] WLLT: Revoked missed ticket bf87c95d568baa86a22b2d9b0338f903a98277968333911b0ff197e750301103 (tx hash: 763ee8603774c40a8f735621db7c8d199dff99e5f8b3214d6bcd09897a464662)
08:43:19 2017-03-02 [INF] WLLT: Connecting block 000000000000061a8113e68ef0ba67f0a6792e7a770f85bfa255efce5d5f24ae, height 111893
08:43:19 2017-03-02 [INF] TMGR: Inserting unconfirmed transaction 763ee8603774c40a8f735621db7c8d199dff99e5f8b3214d6bcd09897a464662
08:57:22 2017-03-02 [ERR] WLLT: Cannot handle chain server voting notification MissedTickets: Error encountered attempting to create revocation using ticket bf87c95d568baa86a22b2d9b0338f903a98277968333911b0ff197e750301103: -22: TX rejected: transaction already exists
08:57:22 2017-03-02 [INF] WLLT: Connecting block 00000000000003dec8ab8b1d56e08787bfa46ccb9e74d9ac8746a1e998cc7196, height 111894
09:00:13 2017-03-02 [INF] WLLT: Connecting block 0000000000000317128a57f9ac382523e5bc5554c9e802b32067cc350a6f1318, height 111895
09:03:50 2017-03-02 [INF] WLLT: Connecting block 0000000000000521fc1242064c8ceba8ba14235bb531053e3ec6458f47110842, height 111896

I had a ticket revoked this morning. I was online (solo staking) and this is what the wallet output looked like.
Can someone explain in plain english why this happened and what I could have done to avoid it?

(I'll link to slack as well)

I don't think it actually revoked. As far as I know, tickets only revoke if they reach their expiration without being used to vote. I think your ticket was called to vote one block before it expired. The unconfirmed vote blocked the ticket expiration/revocation. The wallet tried to revoke the ticket, but couldn't because it was just called to vote in the previous block.

I could be wrong

Missed tickets are also considered revoked... or is it the other way around?
From getstakeinfo I see that I have two tickets total that were both missed and revoked.

The first one was months ago. I had a computer crash and was offline several hours before I could tend to it.
The second was the one I posted about. Missed and revoked while wallet and daemon were online (and unlocked of course)