There are rare cases where ref announcements may be sent in close succession, and the current clock time is re-used. This will cause the second (newer) announcement to be ignored by peers. We add a `timestamp` method that checks if the timestamp is re-used, and increments it if so, ensuring that we always use a fresh one. |
||
|---|---|---|
| .. | ||
| src | ||
| Cargo.toml | ||
| Dockerfile | ||
| build.rs | ||