Using spaces in keys of RPC JSON responses

[cronicc]

The key values in RPC JSON commands inherited from BTC/ZEC all use camel case. We use spaces in many of the newly added commands. This is inconsistent with the style of the existing API and although it's valid JSON it can be cumbersome/problematic to use in many languages (backslash escapes or quoting needed).