mirror of
https://github.com/ElementsProject/lightning.git
synced 2024-12-28 01:24:42 +01:00
ba7d4a8f6b
We were including the entire list of prerequisites when generating a shastamp, which for schemas includes the `tools/fromschema.py` doc. This meant all of our shasums were updating anytime this tool file changed. Instead, we just include the first prerequisite. See: https://www.gnu.org/software/make/manual/html_node/Automatic-Variables.html#Automatic-Variables
45 lines
1.3 KiB
Markdown
45 lines
1.3 KiB
Markdown
lightning-signmessage -- Command to create a signature from this node
|
|
=====================================================================
|
|
|
|
SYNOPSIS
|
|
--------
|
|
|
|
**signmessage** *message*
|
|
|
|
DESCRIPTION
|
|
-----------
|
|
|
|
The **signmessage** RPC command creates a digital signature of
|
|
*message* using this node's secret key. A receiver who knows your
|
|
node's *id* and the *message* can be sure that the resulting signature could
|
|
only be created by something with access to this node's secret key.
|
|
|
|
*message* must be less that 65536 characters.
|
|
|
|
RETURN VALUE
|
|
------------
|
|
[comment]: # (GENERATE-FROM-SCHEMA-START)
|
|
On success, an object is returned, containing:
|
|
- **signature** (hex): The signature (always 128 characters)
|
|
- **recid** (hex): The recovery id (0, 1, 2 or 3) (always 2 characters)
|
|
- **zbase** (string): *signature* and *recid* encoded in a style compatible with **lnd**'s [SignMessageRequest](https://api.lightning.community/#grpc-request-signmessagerequest)
|
|
|
|
[comment]: # (GENERATE-FROM-SCHEMA-END)
|
|
|
|
AUTHOR
|
|
------
|
|
|
|
Rusty Russell <<rusty@rustcorp.com.au>> is mainly responsible.
|
|
|
|
SEE ALSO
|
|
--------
|
|
|
|
lightning-checkmessage(7)
|
|
|
|
RESOURCES
|
|
---------
|
|
|
|
Main web site: <https://github.com/ElementsProject/lightning>
|
|
|
|
[comment]: # ( SHA256STAMP:137e80fcb45c2e93058a869cb991c4aac31dace621f5941e91b9039290659648)
|