Can somebody confirm that default state-pruning and blocks-pruning modes for liberland node are archive-cannonical? Meaning the validator node stores just the minimal set of data it needs to function as a validator? I think that is the case, but I’m not sure, and currently am looking for a way current setting can be examined while the node is running (preferrably).
If you run the node, you will be able to run commands to examine how it works. Those you find on docs.liberland.org. If you want to go a level deeper than that, you can examine the open source code on github. If you want a more, shall we say, “functional” explanation, I can ask Dorian the head developer. Shall I?
It’s a bit deeper than infomation available at docs.liberland.org. Actually I was searching for the console command that provides that information, but seems like even such information is not available. Although I’m not sure about it… I can ask Dorian no worries, thank you.
So node by default is run in mode that prunes old data, not requiring much space for its database, but there is “–prunning archive” switch and it makes node keep complete blockchain. Still haven’t found a way to examine what is the type of database is already in local copy of blockchain (if you don’t remember in what mode you started it), but if you put it in wrong mode, it won’t continue on syncing. Once database is initialized, it must stay in that mode.