What problem does your feature solve?
CLI requests to futurenet are failing for contracts that are compiled with an SDK that uses a env interface greater than futurenet.
Eventually env interface version will be versioned by protocol version so this shouldn't be an issue then, but until then it would be nice to allow the CLI to provide a better error message if the env version of the contract being deployed is not ahead of the RPC.
cc @paulbellamy @leighmcculloch
What would you like to see?
An RPC method to get the current env interface version
What alternatives are there?