factomd
factomd copied to clipboard
Factom Daemon
There is an interface used throughout the codebase thought to be responsible for some panics when a nil message hash is encountered. @PaulSnow is working on this
According to the JSON-RPC 2.0 spec: https://www.jsonrpc.org/specification#error_object > The error codes from and including -32768 to -32000 are reserved for pre-defined errors. Any code within this range, but not defined...
The factomd JSON RPC 2.0 API uses HTTP status codes to indicate a JSON RPC Error Response. This make it difficult for generic JSON RPC 2.0 clients to properly handle...
This call: `factom-cli get dbheight 144378` Contains as part of the response: ``` "dbhash": "6dcbd123507b51a386d16815b9159e7e68d6e383a756d123c916222ff452b8a8", "keymr": "d750bca37731519658303f40cbfbb7ab87fad240770fa8aea3af4770334faa86", "header": { "version": 0, "networkid": 4203931042, "bodymr": "63b9981e9d44ae0a3d36a23bed72cf423cf6ef956dd1b49814edc5eb57e2f03d", "prevkeymr": "70bdde669000bd1d67241448b3fd34f08dedc9f4627b03cef2b469528f7c945b", "prevfullhash": "0398c7cb74bc5c79ba3e1c976bdc5d50a467edf1e57c57e8a55ad8b8ec5b45a7", "timestamp":...
When Peer.Address contains an address like "fe80::f6:ecff:fe05:5ffc%eth0", Peer.LocationFromAddress panics due to `index out of range`. The full panic is: ``` panic: runtime error: index out of range goroutine 52 [running]:...
According to https://www.jsonrpc.org/specification#batch servers should accept batch requests from clients, which are an array of request objects. The current API does not accept batch requests and returns an Invalid Request...
Factomd has a dependency on fork https://github.com/FactomProject/ed25519/ The repo that it was forked from actually became the official ed25519 package of the Golang crypo library: https://godoc.org/golang.org/x/crypto/ed25519. I would recommend switching...
According to current documentation of `ack` call (https://docs.factom.com/api#ack), it seems like you need to know chainID of the entry for get entry information. I always thought, that I need chainID...
The API documentation for the `heights` method states: > leaderheight : The current block being worked on by the leaders in the network. This block is not yet complete, but...
This occured on a node testing the new p2p package on **the testnet** during a **fresh sync** but it seems to be an issue that's been around for a while:...