When querying https://testnet-insight.dashevo.org/insight-api/blocks?limit=1, we are sometimes getting a payload with no blocks. This is breaking for us. Such as the one below
{
"blocks": [],
"length": 0,
"pagination": {
"current": "2021-11-24",
"currentTs": 1637798399,
"isToday": true,
"more": false,
"next": "2021-11-25",
"prev": "2021-11-23"
}
}Perhaps related is the fact that https://testnet-insight.dashevo.org/insight-api/status often returns a payload where the blocks value is a number that is far behind.
{
"info": {
"blocks": 616345,
"connections": 11,
"difficulty": 0.002247077821617921,
"errors": "Warning: unknown new rules activated (versionbit 3)",
"insightversion": "3.1.1",
"network": "testnet",
"protocolversion": 70219,
"relayfee": 1.0e-5,
"timeoffset": -1,
"version": 170003
}
}We got this response on Wed, 24 Nov 2021 09:53:38 GMT, a time where the actual tip of the DASH testnet was 618900.
We were only able to reproduce this through programmatic calls. On the browser we always get the right response.
Are we somehow getting answers from a node that is stuck?
When querying
https://testnet-insight.dashevo.org/insight-api/blocks?limit=1, we are sometimes getting a payload with no blocks. This is breaking for us. Such as the one below{ "blocks": [], "length": 0, "pagination": { "current": "2021-11-24", "currentTs": 1637798399, "isToday": true, "more": false, "next": "2021-11-25", "prev": "2021-11-23" } }Perhaps related is the fact that
https://testnet-insight.dashevo.org/insight-api/statusoften returns a payload where theblocksvalue is a number that is far behind.{ "info": { "blocks": 616345, "connections": 11, "difficulty": 0.002247077821617921, "errors": "Warning: unknown new rules activated (versionbit 3)", "insightversion": "3.1.1", "network": "testnet", "protocolversion": 70219, "relayfee": 1.0e-5, "timeoffset": -1, "version": 170003 } }We got this response on Wed, 24 Nov 2021 09:53:38 GMT, a time where the actual tip of the DASH testnet was
618900.We were only able to reproduce this through programmatic calls. On the browser we always get the right response.
Are we somehow getting answers from a node that is stuck?