Nano-node: Why there is always some blocks unchecked?

Created on 17 Jan 2018  路  7Comments  路  Source: nanocurrency/nano-node

I finally get to completely sync (Release 9.0 Ubuntu 64x)
But slowly the "unchecked" started to grow. The "count" is equal the total blocks statistic in https://www.raiblocks.club/blocks, so i think is not that bad.
But it will slow down transactions in the future? These 215 unchecked blocks are always the same problematic blocks?
Should i use the command "clear_unchecked"?

Most helpful comment

Unchecked blocks are blocks which cannot be tied through any chain to the Genesis block which is distributed as part of the Nano software. These blocks can be generated by anyone and added to the network for nodes to attempt to add to the chain as the missing "gap" or intermediate blocks are broadcast.

The plan for the future is to clear unchecked blocks out as either a circular buffer of fixed size or as they expire, or both.

I'm going to close this issue with this explanation and leave the implementation of the plan above to a separate ticket. Please let me know if you have further questions.

All 7 comments

because the transactions are much faster than 5400 RPM hard disks and bandwidth (at least home internet) can handle, so it'll always be behind, and if people start using on RaspPi, it will be even slower. But it's just a matter of time and having more nodes and distributing the workload better

@pocesar This is just outright false, but keeps being brought up as the reason for sync issues for some reason.

Even a fully synced node, which (currently) sees about 5 new blocks per minute will have lots of unchecked blocks. Here is the current status of my node:

{
    "count": "5032691",
    "unchecked": "3203"
}

If you actually look at resource usage (disk i/o and bandwidth), you will notice that they are not saturated at all.

mine is, and a lot of people are reporting massive I/O

My wallet is not doing more than 200kiB/s of disk IO and the number of unchecked blocks keeps growing slowly, but still faster than the number of checked blocks. Something is really wrong here.

My idea is that the cleaning of the brackets just don't work well, it makes you think you are not synced but you are:
schermata-19-14-05-11

EDIT: just after writing this my brackets are cleared and text changes from "syncing" to "running", but just for some minute, then the (154) and "syncing" are back again.

On my server node I tested this

curl -g -d '{ "action": "unchecked_clear" }' '[::ffff:127.0.0.1]:7076' { "success": "" }

and it brings the count to zero. But still wondering what exactly those blocks are and why they grow.

Unchecked blocks are blocks which cannot be tied through any chain to the Genesis block which is distributed as part of the Nano software. These blocks can be generated by anyone and added to the network for nodes to attempt to add to the chain as the missing "gap" or intermediate blocks are broadcast.

The plan for the future is to clear unchecked blocks out as either a circular buffer of fixed size or as they expire, or both.

I'm going to close this issue with this explanation and leave the implementation of the plan above to a separate ticket. Please let me know if you have further questions.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

termhn picture termhn  路  27Comments

elliottneilclark picture elliottneilclark  路  26Comments

cryptocode picture cryptocode  路  17Comments

SergiySW picture SergiySW  路  23Comments

eddieoz picture eddieoz  路  29Comments