-
Notifications
You must be signed in to change notification settings - Fork 231
Description
Аbstract
Is your feature request related to a problem? Please describe.
No, this is not related with problem, this is a future request.
Motivation and Purposes
A clear and concise description of what the problem is. Ex. I'm always frustrated when [I cann't sign and verify messages].
** Specification**
A clear and concise description of what you want to happen. Describe alternatives you've considered
Here: https://username1565.github.io/brainwallet.github.io/#sign
I can sign the messages, by privkey.
Here,
I can verify the messages, and got the signatory address.
But... This all working only for bitcoins and altcoins, not for waves.
I see on the node there is can be possible to sign and verify messages,
using NODE REST API,
with options
post /addresses/signText/{address} or post /addresses/sign/{address}
and
post /addresses/verifyText/{address} or post /addresses/verify/{address} ,
but in this case the address of signatory - must be the node address.
Backwards Compatibility
Can your proposition affect any existing features?
Maybe, no. You can just add the separate option in waves client and waves-lite-client.
Also, will be better to you add the another menu in NODE REST API
to sign and verify the messages by seed, privkey or pubkey, for remote user, not node address.
But will be better to make this client-side, like in that brainwalletx,
and without transfer any personal info, somewhere.
Examples and Implementation
Examples of implementation in other projects?
http://brainwalletx.github.io/ this is open-source and client-side.