Alexis Sellier 4c1aa65f90 node: correct handling of announcement timestamps ... Since we now have three announcement message types, we need at least three timestamps per peer. But even that is not enough, since we don't want to conflate ref announcements for different projects with each other. The solution is to also keep a map of timestamps per peer, for each tracked project. That way we are able to know when a ref announcement is interesting to us or not. Signed-off-by: Alexis Sellier <alexis@radicle.xyz>		2022-10-14 11:59:54 +02:00
..
src	node: correct handling of announcement timestamps	2022-10-14 11:59:54 +02:00
Cargo.toml	Statically link sqlite3	2022-10-12 13:27:45 +02:00