It doesn't make sense when ton-connect sdk has sendTransaction but no signData or signMessage method.
Futher more, following the spec /message?client_id=<to_hex_str(A)>?to=<to_hex_str(B)>&ttl=300&topic=<sendTransaction|signData> and call a POST request with signData, i just get a 200 response with OK
Describe the solution you'd like
Ideally, every crypto wallet under the sun supports arbitrary message signing, as it's one of the core tenants of private key management. TON development could be 100x easier because it can look at all the other established ecosystems and take the best parts from it. Yet with over 3 issues opened about this, no one seems to care or addresses this requirement
Is your feature request related to a problem?
It doesn't make sense when ton-connect sdk has
sendTransactionbut nosignDataorsignMessagemethod. Futher more, following the spec/message?client_id=<to_hex_str(A)>?to=<to_hex_str(B)>&ttl=300&topic=<sendTransaction|signData>and call a POST request withsignData, i just get a 200 response with OKDescribe the solution you'd like
Ideally, every crypto wallet under the sun supports arbitrary message signing, as it's one of the core tenants of private key management. TON development could be 100x easier because it can look at all the other established ecosystems and take the best parts from it. Yet with over 3 issues opened about this, no one seems to care or addresses this requirement
Describe alternatives you've considered
No response
Additional context
No response