Have net_version also return the paratime version

[nhynes]

It's good for debugging

[CedarMist]

The paratime or other component versions (e.g. keymanager, oasis-core etc) can't be returned in net_version as it could break clients who are expecting a consistent integer network id across multiple software upgrades.

oasis-web3-gateway makes no distinction between chain ID & network ID.

Currently net_version returns chain ID, as is required & documented:

• oasis-web3-gateway/rpc/net/api.go

  Line 22 in 2fa2ad9

  func (api *publicAPI) Version() string {

And eth_chainId works as is required & documented:

• oasis-web3-gateway/rpc/eth/api.go

  Line 286 in 2fa2ad9

  func (api *publicAPI) ChainId() (*hexutil.Big, error) {

A better candidate would be web3_clientVersion ?

• oasis-web3-gateway/rpc/web3/api.go

  Line 32 in 2fa2ad9

  return fmt.Sprintf("oasis/%s/%s", version.Software, version.Toolchain)

Or a custom oasis_paratime API call, which returns the paratime & platform version infos? Then could return a dictionary with necessary info.

Or could use a response header, X-Oasis-Paratime: Sapphire/0.5.2 ?

[nhynes]

Great analysis and suggestions. For context, the debugging scenario mentioned in the issue description happens after a runtime upgrade and gateways may straggle. The version does not necessarily need to be visible to the client, and in an ideal world, not even the developer–the gateways should just upgrade. I have also not missed not having this feature since the time the issue was created, so my current assumptions may be skewed.

In context, an X-Oasis-Runtime header is useful since the deployment on the ground usually has just one straggler gateway behind a load balancer, which wouldn't be obvious just from oasis_getRuntime. This form is also visible to web3 clients with fetch as a bonus.