You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Quantus team, I'm having an issue syncing a fresh Planck node and would appreciate some help. Environment
Quantus Node: v1.0.1-f1176cea6a6
Miner: v4.1.0
OS: Ubuntu 24.04.4 LTS
GPU: RTX 5090
Chain: planck
Sync mode: full
Started using the official quantus-mining.sh script
Problem
My node cannot complete synchronization with the Planck network.
Initially the node synced normally at hundreds of blocks/sec, but later became stuck around block #17k while the network target was around feat: Simple ranked collective #1,081,2xx.
I initially suspected database corruption, so I completely stopped the mining stack and purged the Planck database:
quantus-node purge-chain --chain planck --base-path /root/.local/share/quantus-node
Then I started only the node, without the miner, and performed a completely fresh sync from genesis.
The fresh sync initially worked normally:
Preparing 335.0 bps
Syncing 233.4 bps
but then it became stuck again at:
best: #16896
finalized: #16716
target: #1081242
with repeated:
Syncing 0.0 bps
Eventually I received this error repeatedly:
Block import error: Potential long-range attack: block not in finalized chain.
Error importing block ... consensus error: Import failed: Potential long-range attack: block not in finalized chain.
On the previous sync attempt I also saw repeated:
block has an unknown parent
I verified that v1.0.1 was the latest release at the time.
Could you please confirm:
Is the current Planck network healthy?
Has Planck recently been reset/forked or had its chain history changed?
Is v1.0.1 still compatible with the current Planck network?
Are there updated bootnodes or a newer chain spec I should use?
Is there a snapshot / fast-sync method available instead of syncing from genesis?
Since a completely fresh database reproduces the issue at approximately the same early block height, it doesn't appear to be caused by my previous local database.
Thanks!
Hi Quantus team, I'm having an issue syncing a fresh Planck node and would appreciate some help. Environment
Problem
My node cannot complete synchronization with the Planck network.
Initially the node synced normally at hundreds of blocks/sec, but later became stuck around block #17k while the network target was around feat: Simple ranked collective #1,081,2xx.
I initially suspected database corruption, so I completely stopped the mining stack and purged the Planck database:
quantus-node purge-chain --chain planck --base-path /root/.local/share/quantus-node
Then I started only the node, without the miner, and performed a completely fresh sync from genesis.
The fresh sync initially worked normally:
Preparing 335.0 bps
Syncing 233.4 bps
but then it became stuck again at:
best: #16896
finalized: #16716
target: #1081242
with repeated:
Syncing 0.0 bps
Eventually I received this error repeatedly:
Block import error: Potential long-range attack: block not in finalized chain.
Error importing block ... consensus error: Import failed: Potential long-range attack: block not in finalized chain.
On the previous sync attempt I also saw repeated:
block has an unknown parent
I verified that v1.0.1 was the latest release at the time.
Could you please confirm:
Since a completely fresh database reproduces the issue at approximately the same early block height, it doesn't appear to be caused by my previous local database.
Thanks!
我特别加了第 4、5 个问题。 这两个其实很关