Right, lets do this again, but trying to do it in a better way...
I am doing tests with my newly awaited #HIVE node (still under alpha testing and construction). And as I did some time ago, I need people to do guesses on how long it will take to fully get in sync!
This time I will make it harder to guess because, I am also downloading the chain directly from others (later I will do a local replay too, perhaps another #giveaway).
And to make this fun, I (aka @forykw) am going to award ONE delegation of 2023 HIVE for 2 months! - for the closest guess after this post curation ends.
You can go as granular as milliseconds! 😋 And ANY HIVE account can apply as many times you wish! 😁 BUT, I will consider your latest valid reply ONLY!
(this is to allow for more than one guess, although your last guess should be the "final one")
Suggestions on how to reply? (don't forget, convert your timings to UTC date, and you can use this website to understand a bit more on how to do that... https://currentmillis.com - super geeky I know, sorry 😆 the dark force is with me)
Example (2023 year, December, 23, 6:28 AM UTC, at the 32 seconds and 122 milliseconds) - this date has already elapsed for exemplary reasons:
2023-12-23T06:28:32.122
The sync start in UTC timezone!
------------------------------------------------------
@ @@@@@@ ,@@@@@%
@@@@ (@@@@@* @@@@@@
%@@@@@@ @@@@@@ %@@@@@,
@@@@@@@@@@ @@@@@@ @@@@@@
,@@@@@@@@@@@@ @@@@@@ @@@@@@
@@@@@@@@@@@@@@@& @@@@@@ @@@@@@
@@@@@@@@@@@@@@@@@@ .@@@@@% @@@@@@
@@@@@@@@@@@@@@@@@@@@@( .@@@@@%
@@@@@@@@@@@@@@@@@@@@ @@@@@@
*@@@@@@@@@@@@@@@@ @@@@@@ @@@@@@.
@@@@@@@@@@@@@@ &@@@@@. @@@@@@
#@@@@@@@@@@ @@@@@@ #@@@@@/
@@@@@@@@ /@@@@@/ @@@@@@
@@@@@( @@@@@@ .@@@@@&
@@ @@@@@& @@@@@@
STARTING HIVE NETWORK
------------------------------------------------------
initminer public key: STM8GC13uCZbP44HzMLV6zPZGwVQ8Nt4Kji8PapsPiNq1BK153XTX
chain id: 0000000000000000000000000000000000000000000000000000000000000000
blockchain version: 1.27.5
------------------------------------------------------
hived git_revision: "0acce16829c0702ac09d9e51beb57b9fac157c22"
2023-12-23T06:28:32.121 application.cpp:174 load_logging_config ] Logging thread started
2023-12-23T06:28:32.121 main.cpp:127 main ] Backtrace on segfault is enabled.
Setting up a startup_io_handler...
2023-12-23T06:28:32.122 chain_plugin.cpp:1084 plugin_startup ] Chain plugin initialization...
2023-12-23T06:28:32.122 chain_plugin.cpp:605 initial_settings ] Starting chain with shared_file_size: 23622320128 bytes
2023-12-23T06:28:32.122 chain_plugin.cpp:1088 plugin_startup ] Database opening...
2023-12-23T06:28:32.122 chain_plugin.cpp:687 open ] Opening shared memory from /dev/shm/
2023-12-23T06:28:32.130 decoded_types_data_storage.cpp:97 ~decoded_types_data_ ] decoded_types_data_storage object has been deleted. Decoded types map size: 186
2023-12-23T06:28:32.151 block_log.cpp:161 open ] Opening blocklog ~/hived/datadir/blockchain/block_log
2023-12-23T06:28:32.151 block_log_artifacts.cpp:320 open ] Opening artifacts file ~/hived/datadir/blockchain/block_log.artifacts in read & write mode ...
2023-12-23T06:28:32.151 block_log_artifacts.cpp:327 open ] Could not find artifacts file in ~/hived/datadir/blockchain/block_log.artifacts. Creating new artifacts file ...
2023-12-23T06:28:32.151 block_log_artifacts.cpp:443 flush_header ] Attempting to write header (pack_size: 56) containing: git rev: 0acce16829c0702ac09d9e51beb57b9fac157c22, format version: 1.1, head_b lock_num: 0, tail_block_num: 0, generating_interrupted_at_block: 0, dirty_close: 1
2023-12-23T06:28:32.151 database.cpp:229 load_state_initial_d ] Loaded a blockchain database holding a state specific to head block: 0 and last irreversible block: 0
2023-12-23T06:28:32.151 database.cpp:233 operator() ] Attempting to rewind all undo state...
2023-12-23T06:28:32.151 database.cpp:237 operator() ] Rewind undo state done.
2023-12-23T06:28:32.151 database.cpp:247 operator() ] Blockchain state database is AT IRREVERSIBLE state specific to head block: 0 and LIB: 0
2023-12-23T06:28:32.151 chain_plugin.cpp:1091 plugin_startup ] Looking for snapshot processing requests...
2023-12-23T06:28:32.151 chain_plugin.cpp:1107 plugin_startup ] Consistency data checking...
2023-12-23T06:28:32.151 chain_plugin.cpp:1122 plugin_startup ] P2P enabling...
2023-12-23T06:28:32.151 chain_plugin.cpp:768 work ] Started on blockchain with 0 blocks, LIB: 0
2023-12-23T06:28:32.151 chain_plugin.cpp:774 work ] Started on blockchain with 0 blocks
2023-12-23T06:28:32.151 chain_plugin.cpp:1128 plugin_startup ] Chain plugin initialization finished...
2023-12-23T06:28:32.151 p2p_plugin.cpp:466 plugin_startup ] P2P plugin startup...
2023-12-23T06:28:32.152 webserver_plugin.cpp:247 operator() ] start processing ws thread
2023-12-23T06:28:32.152 webserver_plugin.cpp:268 operator() ] start listening for http requests on 0.0.0.0:8090
2023-12-23T06:28:32.152 webserver_plugin.cpp:270 operator() ] start listening for ws requests on 0.0.0.0:8090
2023-12-23T06:28:32.152 chain_plugin.cpp:356 operator() ] Write processing thread started.
2023-12-23T06:28:32.153 p2p_plugin.cpp:482 operator() ] Configuring P2P to listen at 0.0.0.0:2001
I will post the screenshot of the node log when it finishes the sync and starts getting into normal block fetch!
Clues! 😈
The new system uses DDR5, has more than 16 cores of an undisclosed CPU brand, 1 PCIe 4.0 NVMe and is connected to the internet through 1 Gbps link/ISP. 😜