syscoin / syscoin

Syscoin is a crypto currency that is universally merge-mineable with a dual chain architecture both UTXO and EVM. The UTXO chain offers a data availability layer (Proof-Of-Data Availability) to offer censorship resistance for a rollup-driven roadmap.
https://www.syscoin.org
MIT License
181 stars 71 forks source link

Can't sync tesnet with -chain=test which is apparently not equivalent to -testnet #493

Closed develCuy closed 2 years ago

develCuy commented 2 years ago

With -chain=test, latest syscoind official build can only sync headers up to ~43.47%. Then I try a build from branch dev-4.x, headers sync up to ~65.72%

Expected behavior

Sync blockchain 100%

Actual behavior

Latest official build:

2022-07-07T06:28:15Z Synchronizing blockheaders, height: 544000 (~43.47%)                                                                        
2022-07-07T06:28:16Z Warning: not punishing manually connected peer 0!                                                                           
2022-07-07T06:29:57Z CMasternodeSync::ProcessTick -- skipping mnsync restrictions for peer=0  

Dev build up to commit a527b4e2af12619633ffb09ede5bf38798aa455f:

2022-07-08T16:26:43Z Synchronizing blockheaders, height: 544000 (~65.72%)
2022-07-08T16:26:44Z Warning: not punishing manually connected peer 0!
2022-07-08T16:30:21Z CMasternodeSync::ProcessTick -- skipping mnsync restrictions for peer=0

To reproduce

Run syscoin -chain=test and wait for sync

System information

Syscoin 4.3.0 and dev-4.x (self-compiled) Ubuntu 20.04 LTS HDD

sidhujag commented 2 years ago

hey we have not migrated testnet with dev-4.x for PoDA yet.. we need to update the geth binaries to reflect the changes for PoDA.. technically your node should sync up to 840000 which is where NEVM started on testnet.. 544k is weird it maybe is stuck on utxo assets which started on 545k as well as dip0003 (chainlock and deterministic masternodes).. would be good to see in the log if there are any errors (debug.log)

sidhujag commented 2 years ago

you can try again and use ./syscoind --testnet to run tetnet closing for now open up if issues still