API breaking change in network version numbering

[Stebalien]

Checklist

• This is not a security-related bug/issue. If it is, please follow please follow the security policy.
• This is not a question or a support request. If you have any lotus related questions, please ask in the lotus forum.
• This is not a new feature request. If it is, please file a feature request instead.
• This is not an enhancement request. If it is, please file a improvement suggestion instead.
• I have searched on the issue tracker and the lotus forum, and there is no existing related issue or discussion.
• I am running the Latest release, or the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.
• I did not make any code changes to lotus.

Lotus component

lotus JSON-RPC API

Lotus Version

master

Describe the Bug

See: filecoin-project/go-state-types#30 (comment)

Changing the network version numbers (1 -> 100, etc.) is technically API breaking. We either need to bump the API version, or handle this somehow.

Now, we can handle one half pretty easily: if we're a "lite" node, we can "upgrade" version numbers by multiplying all version numbers less than 100 by 100.

The tricky part is that anything consuming the API will still be broken. Unfortunately, there likely is no good way to fix that without bumping the API version.

Logging Information

None.

Repo Steps

No response