GitBook: [#175] No subject

Author: Leo Weese

SUMMARY.md

@@ -51,6 +51,7 @@
   * [Quick Tor Setup](lightning-network-tools/lnd/quick-tor-setup.md)
   * [Configuring Tor](lightning-network-tools/lnd/configuring\_tor.md)
   * [Enable ‘Neutrino mode’ in Bitcoin Core](lightning-network-tools/lnd/enable-neutrino-mode-in-bitcoin-core.md)
+  * [Send messages with keysend](lightning-network-tools/lnd/send-messages-with-keysend.md)
   * [Debugging LND](lightning-network-tools/lnd/debugging\_lnd.md)
   * [Fuzzing LND](lightning-network-tools/lnd/fuzz.md)
   * [LND and etcd](lightning-network-tools/lnd/etcd.md)

lightning-network-tools/lnd/amp.md

@@ -10,13 +10,13 @@ Atomic Multi-path Payments are a new type of Lightning payments implemented by l
 
 Atomic Multi-path payments differ from existing Multi-path Payments (MPP) in that they are atomic, meaning despite being routed through separate paths. In MPPs, all shards use the same payment hash, making the individual routes easily correlatable and prone to only partial settlement. By contrast AMPs are either settled in full or not settled at all. Using AMP, it is possible to make payments safely by only knowing the public key of the recipient. It is also possible to create invoices that can be used repeatedly, which can be used to implement traditional subscriptions. Such invoices can also be published without security implications, allowing for use cases such as static donation invoices.
 
-|                       | Atomic Multi-path Payments                      | Keysend                              |
-| --------------------- | ----------------------------------------------- | ------------------------------------ |
-| Information necessary | Only node ID                                    | Only node ID                         |
-| Preimage              | Generated by sender, but only known by receiver | Generated and known by the sender    |
-| Multi-path            | Each shard carries its own payment hash         | All shards use the same payment hash |
-| TLV Onion             | Required                                        | Required                             |
-| Static invoices       | Allows for static invoices                      | Does not allow for invoices at all   |
+|                       | Atomic Multi-path Payments                                               | Keysend                              |
+| --------------------- | ------------------------------------------------------------------------ | ------------------------------------ |
+| Information necessary | Only node ID                                                             | Only node ID                         |
+| Preimage              | Generated by sender, but only known by receiver once all shards are paid | Generated and known by the sender    |
+| Multi-path            | Each shard carries its own payment hash                                  | All shards use the same payment hash |
+| TLV Onion             | Required                                                                 | Required                             |
+| Static invoices       | Allows for static invoices                                               | Does not allow for invoices at all   |
 
 In a regular Lightning payment, the payee generates a preimage and transmits its hash as part of the invoice. The Hash Time-lock Contract (HTLC) pays to this hash, and to claim their payment, the payee reveals the preimage, allowing everyone along the route to finalize the payment.
 
@@ -67,12 +67,14 @@ Example usage:
 Switching from MPP to AMP is easy. You will have to replace the `--key_send` flag with a `--amp` flag. You will no longer have to manually generate a preimage as the sender.
 
 **old:**\
-`lncli sendpayment --dest <destination public key> --amt <amount> --key_send`
+`lncli sendpayment --dest <destination public key> --amt <amount> --keysend`
 
 **new:**\
 `lncli sendpayment --dest <destination public key> --amt <amount> --amp`
 
-If you are currently using keysend over the RPC layer, you will be able to smoothly switch over by simply setting the amp field. It is no longer necessary to manually generate and set a preimage.&#x20;
+If you are currently using keysend over the RPC layer, you will be able to smoothly switch over by simply setting the amp field. It is no longer necessary to manually generate and set a preimage.
+
+[Learn: How to send messages with keysend](send-messages-with-keysend.md)
 
 {% content-ref url="amp.md" %}
 [amp.md](amp.md)

lightning-network-tools/lnd/send-messages-with-keysend.md

@@ -0,0 +1,66 @@
+---
+description: >-
+  Learn how to send messages to anyone in the Lightning Network from the command
+  line
+---
+
+# Send messages with keysend
+
+Keysend allows users in the Lightning network to send payments to others , directly to their public key, as long as their node has public channels and has keysend enabled. Keysend does not require the payee to issue an invoice.
+
+This payment type can also be used to attach messages and other data.
+
+Keysend is currently implemented in LND in two ways, the widely accepted “`--keysend`” and the newer “[`--amp`](amp.md)”
+
+## Enable your node to receive keysend
+
+To make sure you are able to receive spontaneous payments, add the following lines to your `lnd.conf` file:
+
+`accept-amp=1`\
+`accept-keysend=true`
+
+Then restart your node with `lncli stop` and `lnd`.
+
+If you want to accept spontaneous payments using AMP, you may also create an invoice with routing hints and distribute it to prospective payers. You can use the command:
+
+`lncli addinvoice –amp`
+
+You can optionally also specify an amount (`--amt`), expiry (`--expiry`), a memo (`--memo`) routing hints are needed if your node only has private channels (`--private`).
+
+## Send a spontaneous payment
+
+To send a spontaneous payment, you can craft a command like this:
+
+`lncli sendpayment --dest <destination public key> --amt <amount> --keysend`
+
+or using AMP (recommended):
+
+`lncli sendpayment --dest <destination public key> --amt <amount> --amp`
+
+### Paying AMP invoices
+
+If the payee has a private node without public channels, they can create an AMP invoice and include routing hints as explained above. The payer can then pay this invoice with the command:
+
+`lncli payinvoice <invoice>`
+
+If an amount is not set in the invoice, it can be set by the payer with&#x20;
+
+`lncli payinvoice <invoice> –amt <amount>`
+
+## Send a message to other nodes
+
+You can include messages into your spontaneous payments with the `–data` flag. It must follow the convention `<record_id>=<hex_value>,<record_id>=<hex_value>,..`
+
+Messages are typically sent with the record ID `34349334`. You can find a registry for such records [here](https://github.com/satoshisstream/satoshis.stream/blob/main/TLV\_registry.md). You may also submit your own suggestions.
+
+You can encode any data in hex, either using your favorite command line or web tool.
+
+The phrase “`Happy Genesis Block Day!`” becomes `48617070792047656E6573697320426C6F636B2044617921`
+
+The full command below will send this message together with 10 satoshis to [Amboss.space](https://amboss.space), where it is displayed publicly.
+
+`lncli sendpayment --dest 03006fcf3312dae8d068ea297f58e2bd00ec1ffe214b793eda46966b6294a53ce6 --amt 10 --data 34349334=48617070792047656E6573697320426C6F636B2044617921 --keysend`
+
+If the payee has created an AMP invoice, the data can also be appended to the command:
+
+lncli payinvoice \<invoice> --data 34349334=486170707920477265676F7269616E204E6577205965617220746F2065766572796F6E65206174204C696768746E696E67204C61627321