rpc: decide on versioning

[distractedm1nd]

We need to make a decision on how we want to version our RPC. In the future we could provide multiple versions at multiple endpoints. At the very least, it will be a failsafe for someone accidentally trying to use an old version of our api

We can then provide the first RPC at /v1 for example

Also: return it as part of node.Info

[renaynay]

We can add standard versioning to the gateway starting at v1 but for json rpc, I propose just versioning it via an endpoint that can be provided on the NodeModule since that's where all admin-related info lives. In Lotus, they just have an endpoint on the common API that returns the version as an encoded uint32. I feel like it's overkill and we can just return a string :)

[Wondertan]

String is fine to me, although I would ask them why the made it as uint32

[renaynay]

Alternatively, we could explore something related to the discussion here. But IMO this is a later consideration and something we should think about from a devX perspective (probably loop in @YazzyYaz)

[renaynay]

As another alternative, we could think about versioning the namespaces under which our modules are registered, but I think that's hairy.

[Wondertan]

As another alternative, we could think about versioning the namespaces under which our modules are registered, but I think that's hairy.

This is the correct approach IMO. Wouldn't say it's hairy but it adds some overhead for sure.

[renaynay]

🤷🏻

I think we can just use a string until further notice.