mirror of
https://github.com/aljazceru/lightning.git
synced 2025-12-23 17:14:22 +01:00
bcabb3825f
1. If the tool changes, you need to regenerate since the output may change. 2. This didn't just filter that out, ignored all but the first dependency, which made bisecting the bookkeeper plugin a nightmare: it didn't regenerate the .po file, causing random crashes. If we want this, try $(filter-out tools/fromschema.py) instead. But I don't think we want that. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
46 lines
1.3 KiB
Markdown
46 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:163cdae723e4b50715255b233ff2a817481ccff0b778d56c2ed0b88bd0cdc8a6)
|