can't 'signmessage' without wallet support compiled in #7895

issue dooglus opened this issue on April 16, 2016

dooglus commented at 8:22 PM on April 16, 2016: contributor

I would like to be able to sign messages using 'signmessage' by providing the private key to the RPC, just like I can 'signrawtransaction'.

If I move 'signmessage' into the 'util' category alongside 'verifymessage' and allow it to take an optional private key parameter would my change stand a chance of being merged?

Currently 'signmessage' isn't even available when I don't build with wallet support since it is considered a wallet function.
achow101 commented at 8:25 PM on April 16, 2016: member

Go ahead and try, it doesn't hurt to try.
btcdrak commented at 8:38 PM on April 16, 2016: contributor

Seems like a reasonable ask to me. Concept ACK.
dooglus commented at 9:28 PM on April 16, 2016: contributor

#7899 adds the optional parameter to signmessage but leaves signmessage in the wallet category.
luke-jr commented at 12:45 AM on April 17, 2016: member

I don't see why a server is needed for this. Should just be a library function.
jonasschnelli added the label Utils and libraries on Apr 17, 2016
laanwj commented at 9:59 AM on April 28, 2016: member

#7953 Create signmessagewithprivkey rpc
laanwj closed this on Jan 26, 2017
MarcoFalke locked this on Sep 8, 2021

Contributors

Labels