Author | SHA1 | Message | Date |
---|---|---|---|
Marko |
044f1bf288
|
format: add format cmd & goimport repo (#4586)
* format: add format cmd & goimport repo - replaced format command - added goimports to format command - ran goimports Signed-off-by: Marko Baricevic <marbar3778@yahoo.com> * fix outliers & undo proto file changes |
5 years ago |
Prince Sinha | 7be74c73b7 |
rpc: add method block_by_hash (#4257)
* added RPC method block_by_hash * created hash => height * changes typings * block_by_hash changes * Update store/store.go Co-Authored-By: Anton Kaliaev <anton.kalyaev@gmail.com> * Update store/store.go Co-Authored-By: Anton Kaliaev <anton.kalyaev@gmail.com> * Update store/store.go Co-Authored-By: Anton Kaliaev <anton.kalyaev@gmail.com> * Update store/store.go Co-Authored-By: Anton Kaliaev <anton.kalyaev@gmail.com> Co-authored-by: Marko <marbar3778@yahoo.com> Co-authored-by: Anton Kaliaev <anton.kalyaev@gmail.com> |
5 years ago |
Anton Kaliaev |
59da313bc0
|
rpc: /block_results fix docs + write test + restructure response (#3615)
BREAKING Example response: ```json { "jsonrpc": "2.0", "id": "", "result": { "height": "2109", "txs_results": null, "begin_block_events": null, "end_block_events": null, "validator_updates": null, "consensus_param_updates": null } } ``` Old result consisted of ABCIResponses struct and height. Exposing internal ABCI structures (which we store in state package) in RPC seems bad to me for the following reasons: 1) high risk of breaking the API when somebody changes internal structs (HAPPENED HERE!) 2) RPC is aware of ABCI, which I'm not sure we want |
5 years ago |
Ethan Buchman | 8dc655dad2 | rpc: fix /blockchain OOM #2049 | 6 years ago |