You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems a node can sometimes find itself in a scenario where pox_is_active on /v2/pox shows true when the amount of stacked stacks is less than the pox activation threshold:
This happened in a closed regtest deployment which resulted in a stall because of pox deactivating, so I'm not sure of the likelihood of this occurring in a bigger open network. But it's still a strange result. It seems internally the node is aware pox is deactivated but the data it displays externally is getting the status from elsewhere that doesn't get updated as frequently.
Here's a link to a chainstate from the aforementioned stalled node in this state: https://drive.google.com/file/d/1NYceDhEEyPPx8FWMA25ce45QC8gzZ4c9/view?usp=sharing
The text was updated successfully, but these errors were encountered:
It seems a node can sometimes find itself in a scenario where
pox_is_active
on/v2/pox
showstrue
when the amount of stacked stacks is less than the pox activation threshold:This happened in a closed regtest deployment which resulted in a stall because of pox deactivating, so I'm not sure of the likelihood of this occurring in a bigger open network. But it's still a strange result. It seems internally the node is aware pox is deactivated but the data it displays externally is getting the status from elsewhere that doesn't get updated as frequently.
Here's a link to a chainstate from the aforementioned stalled node in this state: https://drive.google.com/file/d/1NYceDhEEyPPx8FWMA25ce45QC8gzZ4c9/view?usp=sharing
The text was updated successfully, but these errors were encountered: