lokinet
lokinet copied to clipboard
bundle consensus info into RC
when we think we are going to become an invalid service node (e.g. stake unlock) put the estimated timestamp of when when think it will happen into the RC.
- add time and duration helpers
- make time interally use time points not unix stamps
- fix up unit tests to be a bit cleaner when using cryptomanager
- Router::ModifyOurRC able to be called from any thread by making it interally use EventLoop::call
- add AbstractRouter::InvalidAt to set and unset when our RC is going to be invalid and republish as needed
fixes #1960