Calculating the probability of data persistence

[Profess]

@dirvine

@neo

I implore you to implement the safe storage of the temp key & any required info so that the node can restart where it left off. This also makes archive nodes more easily restartable. Maybe using the weak encryption of the temp key and brute forcing it on restart.

I don’t feel we have a good solition here. The ying yang is this

no encryption
Hackers try and store bad data on nodes to poison the network

in ram key
On reboot you lose the data you held.

safe storage of the temp key
I am still not getting this, but if it’s a key on disk that is guessable then it’s the same problem as no encryption as folk will provide apps to read the data and we are back at square 1 again.

As I say I am not 100% on any track just yet, but it’s not my decision either. It’s worth chatting for sure. I was looking at encrypted volumes and such like, all messy and crappy. I have not found a simple solution here.

Another thing I was pondering was chunks that are so small you could not really hide any bad images and certainly not video in them. Then perhaps we can use entropy checks for detecting text, but only plain text and many text formats have a lot of entropy, but then you can check for file header information, but then again random data will sometimes have valid file header looking info too.

So a few things to think of.

It seems to me , that there is a strong fraction of proponents in the community (of which I include myself), of “restarting the node where it left off” e.g. after a loss of power.

IMHO I firmly believe that solving a solution to this problem would allow the network to gain in several important areas (which I don’t think need to be enumerated).

I have an idea in mind… but first I’d like to make sure - do we have a current definition of the conditions an archive node must meet?

This is probably the most up-to-date discussion about archive nodes:

Update 01 June, 2023

As of yet, not in terms of incentivising. We need to come up with some of those parts. The basics are, we have 2 archive node types DAG or DBC Audit nodes Data archive These will store as much as they can and cover as much of the address space as they can. These will become more important as we go on, I believe. Static or mostly static unread data would be good to push off the frontline nodes. Then we can keep those small and nimble. The DAG nodes will be a really good defence for bad acto…