-
Notifications
You must be signed in to change notification settings - Fork 3
Incorrect activity types logged #34
Comments
Example for the 3rd use case: I picked a random hotspot and compared the bot's output with Helium Explorer. According to the Helium Explorer the hotspot had a "Witness Beacon" activity, 18 witnesses in total, 1 invalid but not from the hotspot we are looking up. The bot's output was
Field parsing from the API is correct in my opinion because the receipt field was null indeed so I assume that the API results are not interpreted correctly. In this case the result should be defined by the following code snippet instead:
That's a redacted snippet from that block in API results that had the valid witness in Explorer and invalid in the bot:
|
Another example, the bot says "Witness Beacon" and the Explorer says "Broadcasted Beacon" for the same event.
|
My assumption was right, Adding |
Comparing the bot's output with Helium Explorer and Hotspotty, I noticed that some activity types are incorrect:
The text was updated successfully, but these errors were encountered: