Add Soroban interface version to getNetwork response

[wildework]

https://github.com/stellar/soroban-tools/blob/967351b064bac431f0d6f9ae61ba6e4f0b417a06/cmd/soroban-rpc/internal/methods/get_network.go#L31C26-L31C26

It would be very useful for the RPC method getNetwork to return the Soroban contract interface version alongside everything else it already returns.

Being able to fetch what Soroban version is deployed on the network exposed through the RPC would allow for a simple check before trying to deploy a new WASM. Makes the endpoint more useful.

[mollykarcher]

Is it possible for this to be exposed by core? Also another question, will the interface version be able to change independent of the protocol version? @anupsdf

[anupsdf]

Is it possible for this to be exposed by core? Also another question, will the interface version be able to change independent of the protocol version? @anupsdf

We have a tracking issue #3960 to provide Soroban network limits to the info endpoint. We can add the contract interface version as well.

[2opremio]

That would be great. Thanks!

[leighmcculloch]

It looks like #3960 was merged at the end of November, so this issue should be unblocked now.

[leighmcculloch]

@wildework made a similar suggestion that fits well with this one to have getNetwork start reporting what versions of the protocol are supported and that are actively in use. I think we can tie that into this issue.

I would be super happy to see the RPC method getNetwork display the range of supported protocol and pre-protocol versions!

Ref: stellar/stellar-protocol#1476 (comment)

Similar to how Horizon already reports the versions available at:

  "current_protocol_version": 20,
  "supported_protocol_version": 20,
  "core_supported_protocol_version": 20

Ref: https://horizon.stellar.org/
Ref: https://horizon-testnet.stellar.org/
Ref: https://horizon-futurenet.stellar.org/