rolling-shutter
rolling-shutter copied to clipboard
collator: Replace REST-API with Eth JSON-RPC
- replace existing OpenAPI with JSON RPC API enpoints
-
/ping
-
/next-epoch
-
/eon
-
/tx
-
with methods under the shutter_
namespace.
Eventually, use the eth_sendRawTransaction
endpoint for the /tx
route.
The proxy
routes have to be kept in sync with this
Any specific reason for this? consistency with the rest of the ecosystem and getting rid of swagger? (also see https://github.com/shutter-network/rolling-shutter/issues/171)
More because of consistency - I think you didn't have geths JSON RPC lib in mind when you were looking for a swagger alternative. But maybe it is a bad idea since the transaction format is non-standard anyways.
I think this is no priority and we should revisit this once we think about user libraries.
Closing this as we don't need the collator anymore