6/12/2023 0 Comments Btcd qt sync![]() ![]() In the above example it has only written the filters up to block 2000 and from there on they are just being stashed. Here is a subset of the above lines for clarity:Īs soon as it has received some of the headers out of order as above, it starts "stashing" the data as it receives it. BTCN: Got response for headers at height=7001, only at height=2000, stashing BTCN: Got cfheaders from height=7001 to height=8001 BTCN: Got response for headers at height=6001, only at height=2000, stashing BTCN: Got cfheaders from height=6001 to height=7001 BTCN: Got response for headers at height=4001, only at height=2000, stashing BTCN: Got cfheaders from height=4001 to height=5001 BTCN: Got response for headers at height=5001, only at height=2000, stashing BTCN: Got cfheaders from height=5001 to height=6001 BTCN: Got response for headers at height=3001, only at height=2000, stashing BTCN: Got cfheaders from height=3001 to height=4001 ![]() BTCN: Writing filter headers up to height=2000 BTCN: Got cfheaders from height=1001 to height=2001 BTCN: Got response for headers at height=2001, only at height=1000, stashing BTCN: Got cfheaders from height=2001 to height=3001 LNWL: Catching up block hashes to height 1384261, this might take a while BTCN: Waiting for filter headers (height=1000) to catch up the rescan start (height=1384261) BTCN: Verified 1 filter header in the last 3m53.05s (height 1, 23:22:08 +0000 UTC) BTCN: Writing filter headers up to height=1000 BTCN: Got cfheaders from height=1 to height=1001 BTCN: Attempting to query for 1384 cfheader batches BTCN: Starting to query for cfheaders from checkpoint_interval=0 BTCN: Received unhandled message of type cfcheckpt from 35.231.86.179:18333 (outbound) BTCN: Received unhandled message of type cfcheckpt from 35.196.85.107:18333 (outbound) BTCN: Starting cfheaders sync for filter_type=0 ![]()
0 Comments
Leave a Reply. |