kopia lustrzana https://github.com/Podcastindex-org/podcast-namespace
Update wording of AMP part
rodzic
9e2e06e4ce
commit
bb350a7026
|
@ -265,12 +265,12 @@ API that exposes a compatible process.
|
||||||
|
|
||||||
Currently, development is centered fully on [Lightning](https://github.com/lightningnetwork) using the "keysend" protocol. Keysend allows for push
|
Currently, development is centered fully on [Lightning](https://github.com/lightningnetwork) using the "keysend" protocol. Keysend allows for push
|
||||||
based payments without the recipient needing to generate an invoice to receive them.
|
based payments without the recipient needing to generate an invoice to receive them.
|
||||||
|
Another method to send spontaneous payments via Lightning is AMP, atomic
|
||||||
|
[multipath payments][AMP]. AMP supersedes keysend in many ways and allows for
|
||||||
|
more robust and larger payments. However, it is still in beta and thus not
|
||||||
|
widely implemented as of now.
|
||||||
|
|
||||||
Atomic multipath payments ([AMPs]) are another, more modern method to send
|
[AMP]: https://bitcoinops.org/en/topics/multipath-payments/
|
||||||
spontaneous payments via lightning. AMP payments require the same information
|
|
||||||
as `keysend` payments, namely a node pubkey and a payment amount.
|
|
||||||
|
|
||||||
[AMPs]: https://bitcoinops.org/en/topics/multipath-payments/
|
|
||||||
|
|
||||||
<br>
|
<br>
|
||||||
|
|
||||||
|
|
Ładowanie…
Reference in New Issue