It would be very useful to have a script that can be run from cron that processes the output of getchaintips and looks for re-orgs which have a branchlen > 1, which is an indication that something "no bueno" is happening. re-orgs of branchlen=1 are very common and should not notify anybody.
This RPC is very fast, so it can be run very often, such as once per minute.
It would be very useful to have a script that can be run from cron that processes the output of `getchaintips` and looks for re-orgs which have a `branchlen` > 1, which is an indication that something "no bueno" is happening. re-orgs of `branchlen=1` are very common and should not notify anybody.
This RPC is very fast, so it can be run very often, such as once per minute.
We also publish this API on the web, so it would be possible to compare local node data against https://explorer.hush.is/api/getchaintips.json and https://explorer.hush.land/api/getchaintips.json . Only nodes which see a re-org will have the data, so some nodes will have different data from others.
onryo
duke
It would be very useful to have a script that can be run from cron that processes the output of
getchaintipsand looks for re-orgs which have abranchlen> 1, which is an indication that something "no bueno" is happening. re-orgs ofbranchlen=1are very common and should not notify anybody.This RPC is very fast, so it can be run very often, such as once per minute.
We also publish this API on the web, so it would be possible to compare local node data against https://explorer.hush.is/api/getchaintips.json and https://explorer.hush.land/api/getchaintips.json . Only nodes which see a re-org will have the data, so some nodes will have different data from others.
Working on this is more important and should be done before the similar InvalidChainFound script