Difference between revisions of "Key send"
Jump to navigation
Jump to search
MiltonPusser (talk | contribs) |
MiltonPusser (talk | contribs) |
||
| Line 1: | Line 1: | ||
Beyond push payments this feature allows for two-way communication with a client. So this can help drive AMP route sharding, CoinJoin negotiations, as well as sending money to friends with emojis or depositing into exchanges with account ids. | Beyond push payments this feature allows for two-way communication with a client. So this can help drive AMP route sharding, CoinJoin negotiations, as well as sending money to friends with emojis or depositing into exchanges with account ids. | ||
=Using key send= | |||
==Receiver side== | |||
Enable in config. accept-keysend=1 in Application options. | |||
==Send to receiver== | |||
lncli sendpayment --dest=03e691f81f08c56fa876cc4ef5c9e8b727bd682cf35605be25d48607a802526053 --final_cltv_delta=144 --amt=100 --keysend | |||
It can enable [[Unilateral (permissionless) payments]] | It can enable [[Unilateral (permissionless) payments]] | ||
Revision as of 19:35, 4 May 2020
Beyond push payments this feature allows for two-way communication with a client. So this can help drive AMP route sharding, CoinJoin negotiations, as well as sending money to friends with emojis or depositing into exchanges with account ids.
Using key send
Receiver side
Enable in config. accept-keysend=1 in Application options.
Send to receiver
lncli sendpayment --dest=03e691f81f08c56fa876cc4ef5c9e8b727bd682cf35605be25d48607a802526053 --final_cltv_delta=144 --amt=100 --keysend
It can enable Unilateral (permissionless) payments