A job that periodically republishes a local LeaseSet to the network database.
This job handles the lifecycle of lease set publication including:
- Initial publication when the router has been running for sufficient uptime
- Periodic republishing before lease expiration (every 7 minutes)
- Retry logic with exponential backoff on publication failure
- Floodfill verification of published lease sets
- Cleanup of expired/stale lease sets when service stops
The job manages a retry mechanism that:
- Retries every 2 seconds on failure
- Elevates to high priority every 4th attempt
- Verifies publication via floodfill peers after 3 failures
- Stops publishing when the client is no longer local
This class is thread-safe and uses concurrent maps for tracking retry state
and logging throttling across multiple instances.