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
We can use this /version API to make 1.1.0 version wallet sending to be compatible with 1.0.x version receiving. The 1.0.x version will return 404 Not Found for this API.
Sending side can detect the receiver's version in all the future versions since 1.1.0.
The text was updated successfully, but these errors were encountered:
I don't think we want to change the endpoint each time the api changes. V1 is the http api, V2 is the json-rpc api, but there is another version number within these that can be retrieved by the check_version function.
Now we have these wallet APIs in
1.1.0
version:How about add a
/version
API since1.1.0
version?/version
API to make1.1.0
version wallet sending to be compatible with1.0.x
version receiving. The1.0.x
version will return404 Not Found
for this API.1.1.0
.The text was updated successfully, but these errors were encountered: