Does this mean that we are actually generating checkpoint files on all the nodes all the time? If so, how much work would it be to have newly installed nodes query for the most recent db files and start with that, instead of redownloading the entire blockchain. Of course, must be peer verified checksums, etc.
I don't understand what you mean by checkpoint file. The rest is a bad idea.
It might be a bad idea, but the problem of how will small machines be able to keep up with 1000TPS volumes is unsolved.
checkpoint file would be "entire state of NXT blockchain" at specific intervals. I am assuming you are not storing the entire blockchain now that we have DB,but maybe that is incorrect?
Almost all NXT functions only need the most recent 1440 blocks, so if each machine kept those 1440 blocks locally, they can purge them after that. blockchain FIFO.
As the blockchain grows, it will take longer and longer for initial install. By having the entire state of NXT every hour, or even every day, in a decentralized peer validated form, would allow starting from the most recent hour (or day) and then start processing blocks from that point.
These two are totally independent technically, but combine to allow small raspis to continue forging and being full nodes
If checkpoint files are a bad idea, I can live with that. Is blockchain FIFO a bad idea too?