search

OmniLayer / omnicore

OmniCore staging tree
http://www.omnilayer.org/
MIT License
759 stars 231 forks source link

Update from the 0.8.2 to 0.9.0 - Scanning starts #1182

Open bogdansharuk opened 4 years ago

bogdansharuk commented 4 years ago

I can not understand... I updated my omnicore node from the version 0.8.2 to 0.9.0

https://github.com/OmniLayer/omnicore/releases/tag/v0.9.0

here it is written :

"Upgrading from 0.8.2, 0.8.1 or 0.8.0 does not require a rescan and can be done very fast without interruption"

but after the update - Scanning starts and now you have to wait a long time

can someone explain why this is happening

Initializing Omni Core v0.9.0 [main]
2020-10-16T08:10:42Z Startup time: 2020-10-16T08:10:42Z
2020-10-16T08:10:42Z txindex is enabled at height 652922
2020-10-16T08:10:42Z txindex thread exit
2020-10-16T08:10:43Z Loading trades database: OK
2020-10-16T08:10:43Z Loading send-to-owners database: OK
2020-10-16T08:10:46Z Loading tx meta-info database: OK
2020-10-16T08:10:47Z Loading smart property database: OK
2020-10-16T08:10:48Z Loading master transactions database: OK
2020-10-16T08:10:48Z Loading fee cache database: OK
2020-10-16T08:10:48Z Loading fee history database: OK
2020-10-16T08:10:48Z Trying to load most relevant state into memory..
2020-10-16T08:10:48Z Failed to load historical state: watermark isn't a real block
2020-10-16T08:10:48Z VerifyTransactionExistence: verifying existence of historical transactions up to block -1..
2020-10-16T08:10:48Z Loading persistent state: NONE (no usable previous state found)
2020-10-16T08:10:48Z Clearing all state..
2020-10-16T08:12:38Z Loading feature activations from levelDB
2020-10-16T08:14:28Z Loading freeze state from levelDB
2020-10-16T08:14:33Z Scanning for transactions in block 249498 to block 652922..
2020-10-16T08:14:33Z Seed block filter active - 82372 blocks will be parsed during initial scan.
2020-10-16T08:14:34Z ____________________________________________________________________________________________________________________________________
2020-10-16T08:14:34Z parseTransaction(block=249498, 2013-07-31T21:32:31Z idx= 23); txid: 546a406a131089e7c2f27d34a93a4d27441d98d096404d6737c5ad5b5e61a09b
2020-10-16T08:14:34Z !! sender: 1PA8qhEzW7to6EeqBAdhVZYGbVj2MfmN2n , receiver: 
2020-10-16T08:14:34Z !! this may be the BTC payment for an offer !!
2020-10-16T08:14:34Z Exodus Fundraiser tx detected, tx 546a406a131089e7c2f27d34a93a4d27441d98d096404d6737c5ad5b5e61a09b generated 2310.91243386
2020-10-16T08:14:34Z update_tally_map(1PA8qhEzW7to6EeqBAdhVZYGbVj2MfmN2n, 1=0x1, +231091243386, ttype=0): before=0, after=231091243386
2020-10-16T08:14:34Z update_tally_map(1PA8qhEzW7to6EeqBAdhVZYGbVj2MfmN2n, 2=0x2, +231091243386, ttype=0): before=0, after=231091243386
2020-10-16T08:14:34Z ____________________________________________________________________________________________________________________________________
Crypto2 commented 3 years ago

Same here unfortunately, was supposed to be a quick update now it'll be down for hours and going to get a ton of complaints :(

Is there a snapshot of the Omni Layer-specific DBs/indexes available anywhere (MP_persist, Omni_TXDB, etc.)?