Does gossipsub have a way to bring a offline node up to speed with the rest of the network?

So from what I understand libp2p gossipsub can get eventual consistency when nodes are online. However, what happens when a node goes offline? I think in the short term (say a network glitch) it should be fine but I am not sure if that is the case if a node goes offline for a longer period. If a node goes offline for a week will it be able to get to the same state as the rest of the nodes? I think I read somewhere that there is message caching but I don’t know how long that cache lasts. At some point it might be more efficient for a node to drop its current state and pull all app data from a different node.

You will want to implement your own protocol for this.

So does gossipsub cache messages? If so how long? I found the documentation to be a bit confusing.

it does for a few seconds.

1 Like

So on boot up I would need to query changes since last power off? That should not be to bad if I just keep a log of all changes. I simply could automatically cap the log size and if the node is to far behind it could just pull a fresh copy of the current state.

Thanks that is really helpful.