More Revoke Weirdness

Discussion in 'Tickets' started by drunkenmugsy, Mar 4, 2016.

Tags:
  1. 2017/12/15 - Decred v1.1.2 released! → Release Notes  → Downloads
  1. drunkenmugsy

    drunkenmugsy Sr. Member
    Advocate (Reddit)

    Dec 28, 2015
    405
    218
    Male
    I just had a revoke come through but it was a little weird. DCRD did not see the next block, 7498, seconds after the block I voted on yet DCRWALLET did. What happen? I was under the impression that the wallet gets info from the local dcrd daemon. How is this possible? Then DCRD processes 2 blocks, 7499 and the missing 7498?


    dcrwallet:
    14:58:43 2016-03-04 [INF] WLLT: Connecting block 00000000000020a778a097f38e1b621e26a2bd7c0572f7bd5c2a40a81da311ee, height 7497
    14:58:46 2016-03-04 [INF] WLLT: Voted on block 00000000000020a778a097f38e1b621e26a2bd7c0572f7bd5c2a40a81da311ee (height 7497) using ticket d0ae87577a8068e545bfb2d9a661c4664c982adad178b09dd61fe5bab0c85020 (vote hash: 705a8552d3709af331845c79c2dbb20b56b9e226152476e78ece708a33651a8f)
    14:58:50 2016-03-04 [INF] WLLT: Connecting block 0000000000003cc4d69053226c0db63e2d01281bd4f20d4ed85b20a93bc695a8, height 7498
    14:58:52 2016-03-04 [INF] WLLT: Revoked missed ticket d0ae87577a8068e545bfb2d9a661c4664c982adad178b09dd61fe5bab0c85020 (tx hash: 521b5a3be4689d1b4845fb805cb81d9109b7bbdde0cd3670e8ddef2de04c2dcc)
    14:58:52 2016-03-04 [INF] TMGR: Inserting unconfirmed transaction 521b5a3be4689d1b4845fb805cb81d9109b7bbdde0cd3670e8ddef2de04c2dcc
    15:03:26 2016-03-04 [INF] WLLT: Connecting block 000000000000408c1dbfde669c53246ab7784517f72fd17c8f44890b0f1c99e5, height 7499

    dcrd:
    14:56:49 2016-03-04 [INF] BMGR: Processed 1 block in the last 13m11.2s (5 transactions, height 7496, 2016-03-04 14:55:49 -0600 CST)
    14:58:46 2016-03-04 [INF] BMGR: Processed 1 block in the last 1m57.1s (1 transaction, height 7497, 2016-03-04 14:57:43 -0600 CST)
    15:03:28 2016-03-04 [INF] BMGR: Processed 2 blocks in the last 4m42.17s (10 transactions, height 7499, 2016-03-04 15:02:56 -0600 CST)
     
  2. drunkenmugsy

    drunkenmugsy Sr. Member
    Advocate (Reddit)

    Dec 28, 2015
    405
    218
    Male
    Here is the same thing again. All with really fast blocks afterwards. Sub 30 second blocks causing a revoke. Is this really latency in my voting or is it just a block going through to fast?

    DCRD:
    12:27:43 2016-03-05 [INF] BMGR: Processed 1 block in the last 1m46.15s (6 transactions, height 7766, 2016-03-05 12:26:50 -0600 CST)
    12:28:01 2016-03-05 [INF] BMGR: Processed 2 blocks in the last 18.49s (2 transactions, height 7768, 2016-03-05 12:27:48 -0600 CST)
    12:28:21 2016-03-05 [INF] BMGR: Processed 1 block in the last 19.75s (2 transactions, height 7769, 2016-03-05 12:28:14 -0600 CST)

    DCRWALLET:
    12:27:40 2016-03-05 [INF] WLLT: Connecting block 0000000000000574f437bb9716a3bcbaaa543353b31304c68fdc280ead2184ca, height 7766
    12:27:43 2016-03-05 [INF] WLLT: Voted on block 0000000000000574f437bb9716a3bcbaaa543353b31304c68fdc280ead2184ca (height 7766) using ticket 85b654955cf59c00c6a3f0d8f4ce3c82e0483d76eb952333669fbd5ee693fe96 (vote hash: 9a90cff91b796c33f5d7de39da974fbde4a6c6cacb1a9d0227258bb2463d6a9b)
    12:27:45 2016-03-05 [INF] WLLT: Connecting block 0000000000000c9ab36b3af5be0727aaa60ef7656c3c105be0cef5ad86ecfada, height 7767
    12:27:47 2016-03-05 [INF] WLLT: Revoked missed ticket 85b654955cf59c00c6a3f0d8f4ce3c82e0483d76eb952333669fbd5ee693fe96 (tx hash: 06f35cddcc700a795bc933782c78fbe5ec607d81aa63339eec1a187ed1fad65b)
    12:27:47 2016-03-05 [INF] TMGR: Inserting unconfirmed transaction 91e72ea7d7303c65b70f7c2bf5d4932bb54dbb973bf9f7100a0acd2046321c38
     
  3. davecgh

    davecgh Hero Member
    Developer Organizer

    Dec 31, 2015
    642
    788
    Male
    United States
    Looks like you voted at 12:27:43 and the next block showed up 2 seconds later. That really isn't a lot of time for the vote to have traversed the network to the miner and for it to recognize it and start working on the solution with the vote included.
     
  4. drunkenmugsy

    drunkenmugsy Sr. Member
    Advocate (Reddit)

    Dec 28, 2015
    405
    218
    Male
    #4 drunkenmugsy, Mar 5, 2016
    Last edited: Mar 5, 2016
    That was my thought. There shouldnt be a new block, 7767, 5 seconds after the time 7766 came down should there?

    I have seen this fast blocking multiple times, more than these 2, all resulting in revokes. What can I do to fix it and not get revokes? If we need to vote in sub 3 second increments I think myself and many other people will have issues making that cut regardless of what type of setup or connection you have to the internet. When you are talking latency/distance its all physics. Light only travels so fast.

    There is no 'minimum next block time' as this would mess up PoW?
     
  5. davecgh

    davecgh Hero Member
    Developer Organizer

    Dec 31, 2015
    642
    788
    Male
    United States
    Correct that there is no minimum next block time. It is not extremely frequent that is a block is found within a few seconds, but it certainly does happen as this case illustrates. As you can see from dcrstats.com the average block time is currently "04:49" which is extremely close to the target of 5 minutes. However, since it's all probabilistic, some blocks are found in a few seconds while others can take up to 20 minutes or longer. Given that the average is slightly under the target, it's likely the block difficulty will rise at the next retarget interval.
     

Share This Page