Skip to content

config: add a flag to skip blocksync if num(peers)=0 and num(vals) > 0 #1679

@czarcas7ic

Description

@czarcas7ic

Bug Report

Many times, we create state exported testnets based on mainnet state. Usually, these networks don't start unless fast sync is set to true, at which point they start. Before knowing this hack, we used "kicker nodes", or nodes we simply peered to the validator to get the network to start. When moving over to comet BFT, I found that the fast sync hack no longer works, and "kicker nodes" are once again required. Removing the following lines prevents the need for a kicker node or the fast sync hack

// Need at least 1 peer to be considered caught up.
if len(pool.peers) == 0 {
pool.Logger.Debug("Blockpool has no peers")
return false
}

I am not sure if just removing those lines is the best way forward, I am just pointing out that there is once again large overhead in creating these state exported testnets, as multiple nodes are once again required. Please let me know if any further information is needed.

Metadata

Metadata

Assignees

Type

No type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions