Andymck/reactivation tweaks by andymck · Pull Request #1361 · helium/blockchain-core

andymck · 2022-05-23T13:36:38Z

Centralises a couple of util functions ,is_gw_active/3 and max_activity_age rather than having this code living in various places.
Check to see if a GW is asserted when processing the reactivation lists in a HB, if not then dont reactivate
Check to see if a GW has already been reactivated when processing the reactivation list in a HB, for example a GW could have been bouncing around validators and been included in the HB from multiple validators. We now check to if it is within the max activity age and if so then dont update its last activity field

TODO: Point 3 of this list may require a chain var ?

andymck force-pushed the andymck/reactivation-tweaks branch 2 times, most recently from 01fe359 to 12f5b44 Compare May 23, 2022 13:40

andymck mentioned this pull request May 23, 2022

dont reactivate unasserted GWs helium/sibyl#53

Open

andymck force-pushed the andymck/reactivation-tweaks branch 3 times, most recently from 7d8f7fb to dab3734 Compare May 24, 2022 09:45

dont reactivate gw if already active

cd7dde3

andymck force-pushed the andymck/reactivation-tweaks branch from dab3734 to cd7dde3 Compare May 24, 2022 09:47

andymck marked this pull request as ready for review May 24, 2022 09:49

Navigation Menu