I built my database from 0 and is now fully synced
. It took a few hrs (overnight) but well worth the wait which included a reboot at around block 28XXXXX. The opened the wallet again and sync continued.
Few hours? On my experience, You are a very lucky man.
)
What are future ideas that can help reduce this sync time. In the future as the database is growing larger and larger
Yes, you are right, the database can only grow, IMHO this is a common
problem with all the cryptocoins in general.
Recently I not followed the new coins, so I don't know there is any
new way or idea to shrink the blockchain database, but I think
it would require a complete redesign of the structure of the cryptocoin
itself.
In some operating systems, you can automatically compress a directory or just some files,
it might seem a simple solution, but in this case IMHO I do not think it's a good idea
because the database files have continuous access, and this continuous de \ compress
the data files may slow down the system too.
To reduce sync time, Shahim proposed an idea of storing on the site a set of
small blockchain datafile, to be loaded by the wallet in case of necessity.
This idea can help, but it don't change the ever growing way of work of wallet.
also I have a few questions please
database - Holds blockchain - can this be zipped and shared
Ehmmm... no. It is used by internal database, but it is not the database.
Its contents change at every installation, and don't grow much.
No need to share.
txleveldb - whats this folder do
Used in some way for the transanction's database and index,
grow with use.
blk0001.dat - whats this dat do
This is THE blockchain database, it grow with every block, with time it grow, grow a lot.
.lock - whats this folder do
db.log - whats this log do
It avoid multiple istances of wallet, and db.log store the log in case of internal
database problem, usually they don't grow.
debug.log -whats this log do
Keep a trace of many wallet's internal activity, and grow a lot, especially in case
of error. If you dig enough is the only way to hypothesize the reason of errors.
If it become too big, usually, it is auto-cutted during the wallet restart.
libgcc_s_dw2-1.dll -whats this dll do
libstdc++-6.dll -whats this dll do
libwinpthread-1.dll -whats this dll do
Dynamic-Link Library, some set of common or standard routine and API for\from GCC, C++,
and Thread used by the PC Win program, in this case the wallet.
peers.dat -whats this dat do
This file store a sort of ip:port phonebook, with the list of other wallets (peer),
those peers form the coin network.
This file is regenerated and continuously updated by wallet, and the element
in list are tested and exchanged between peers, to keep the network working and alive.
summercoinv2.conf -what is the best conf
Good question. The wallet can work even without a conf file, using hard coded value.
In it you can also set some start commandline parameters.
NOTE: The rpcuser and rpcpassword
must never be show to other or shared.
I'm sorry to have given some answers in a hasty or superficial manner, it's late night.
Bye Bye