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
In the last 2 versions of Waves you (assumedly accidentally) broke the entire ability of the wallet to send funds by removing /assets/[transfer,masstransfer,…] from the RPC, and hid them under an expander even versus making a big nice note of it up top. I've never understood the logic coins have of taking their coin with a built-in wallet that can send funds and removing the ability from it without an external SDK to do it instead. Unless someone is using one of the usually 1-3 languages an official SDK is available for they are screwed. The excuse is usually that the request is over the network so it's "insecure", but that is nonsense since the node could be running on the same system bound to 127.0.0.1, over secure VPNs/tunnels, etc.
I don't mean to be a jerk here but I can't speak for anyone else but Waves doesn't do enough volume to rewrite the integration with a new method so we'll just have to delist it before 4.2.0 stops working if the new version isn't fixed.
The text was updated successfully, but these errors were encountered:
In the last 2 versions of Waves you (assumedly accidentally) broke the entire ability of the wallet to send funds by removing /assets/[transfer,masstransfer,…] from the RPC, and hid them under an expander even versus making a big nice note of it up top. I've never understood the logic coins have of taking their coin with a built-in wallet that can send funds and removing the ability from it without an external SDK to do it instead. Unless someone is using one of the usually 1-3 languages an official SDK is available for they are screwed. The excuse is usually that the request is over the network so it's "insecure", but that is nonsense since the node could be running on the same system bound to 127.0.0.1, over secure VPNs/tunnels, etc.
I don't mean to be a jerk here but I can't speak for anyone else but Waves doesn't do enough volume to rewrite the integration with a new method so we'll just have to delist it before 4.2.0 stops working if the new version isn't fixed.
The text was updated successfully, but these errors were encountered: