You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be helpful to supplement this response with the interfaceVersion with a range of supported SDK versions (these are embedded in a WASM custom section). Also, the version/commit for the Soroban environment and XDR that the RPC/network supports.
What problem does your feature solve?
This would allow tool developers to gracefully fail when versions become out of sync between the tool and futurenet or testnet.
What alternatives are there?
I guess you can use the protocolVersion to track down these values by going through the related repositories, but I wouldn't know how to do it.
The text was updated successfully, but these errors were encountered:
Right now
getNetwork
returns the following for testnetIt would be helpful to supplement this response with the
interfaceVersion
with a range of supported SDK versions (these are embedded in a WASM custom section). Also, the version/commit for the Soroban environment and XDR that the RPC/network supports.What problem does your feature solve?
This would allow tool developers to gracefully fail when versions become out of sync between the tool and futurenet or testnet.
What alternatives are there?
I guess you can use the
protocolVersion
to track down these values by going through the related repositories, but I wouldn't know how to do it.The text was updated successfully, but these errors were encountered: