That's not even correct. The DB Filler doesn't read the blockchain and extract the data fully, only partially. If the DB Filler fails, there's a gap in the transactions. It won't pull all the data. For example, if you delete the database of the DB Filler and restart it, it will start from the moment it's turned back on, old data won't be pulled from the blockchain anymore. Try it out. You haven't noticed this after 20 projects? You also didn't notice that invalid blocks are temporarily added? Because all blocks are added in real-time without being checked first? And then later marked as valid or invalid, but counted in the overall score up to pruning points? You haven't noticed this? And no, this has nothing to do with the chain. It's truly amazing what you haven't noticed after 20 projects, such simple things.
But I do find it really cool that you created a new account for this, the third one. It's also a bit scary at times. Did you forget your old passwords or develop another personality? And don't you have anything better to do if you're involved so professionally in 20 projects?
Yes lAmeR1 Kaspa database filler works as you state in case of the explorer database being removed. The database filler in this case will continue from the latest block of the blockchain and continue adding new blocks to the explorer database. Here is why I say that I smell a lie. You are saying that invalid blocks are added to the explorer database and are counted as your premine, but that does not happen because Kaspa and it's forks do not process such blocks. Every block reaching your database filler has been first processed by the network consensus like I previously stated.
Though I understand if you are confusing stuff to transaction confirmations. Since confirmation data is the only thing that is processed after block addition to the explorer database and confirmation data does not matter to the Kaspa wallets and every transaction can be marked as confirmed manually in the database. Only exchanges care about the confirmations, who do not credit transactions before they see that the transactions have been confirmed by the virtual chain.
On another note: We have database fillers available that can crawl information from genesis or any other block to the explorer database, your explorer information can be confirmed right away by third party.
In that sense nothing even close to is believable that you would have extra data in the explorer database. Since removal of such data is simple SQL DELETE.
