-
Notifications
You must be signed in to change notification settings - Fork 92
Open
Description
This report came from @ilzheev in discord. One of the nodes in the open node cluster reported a different factoid balance. The node in question is https://cl.factomd.net, which reports itself as running version 6.7.0 and was, at the time, synced to the latest block (266519).
The FCT address in question is FA3RqGvKruW9BPTPHqRGAop76HgJm4fHoit7wW4aqmPyHtrjCy1M, which is reported at 51.2 FCT by most nodes and 57.6 FCT by the cl node.
I verified it myself by comparing it to my local mainnet node:
who@spoon:~$ curl -d '{"jsonrpc": "2.0", "id": 0, "method": "factoid-balance", "params": {"address": "FA3RqGvKruW9BPTPHqRGAop76HgJm4fHoit7wW4aqmPyHtrjCy1M"}}' https://cl.factomd.net/v2
{"jsonrpc":"2.0","id":0,"result":{"balance":5760000000}}
who@spoon:~$ curl -d '{"jsonrpc": "2.0", "id": 0, "method": "factoid-balance", "params": {"address": "FA3RqGvKruW9BPTPHqRGAop76HgJm4fHoit7wW4aqmPyHtrjCy1M"}}' http://localhost:8088/v2
{"jsonrpc":"2.0","id":0,"result":{"balance":5120000000}}
I have asked Anton to provide the node's FastBoot file so we can see if it's an isolated issue or if there are more differing balances, and we're going to try deleting the FastBoot file and restarting the node to see if that fixes the incorrect state.
Metadata
Metadata
Assignees
Labels
No labels