Difference between revisions of "Lightning"
From Organic Design wiki
(→See also: Accept lightning payments easily with Strike) |
(→See also: Announcing Zap beta release) |
||
Line 8: | Line 8: | ||
*[https://bitcoinmagazine.com/articles/how-the-lightning-network-layers-privacy-on-top-of-bitcoin-1482183775/ How privacy will be done with Lightning] | *[https://bitcoinmagazine.com/articles/how-the-lightning-network-layers-privacy-on-top-of-bitcoin-1482183775/ How privacy will be done with Lightning] | ||
*[https://medium.com/@ACINQ/introducing-strike-a-stripe-like-api-for-lightning-c84762f4f634 Accept lightning payments easily with Strike] | *[https://medium.com/@ACINQ/introducing-strike-a-stripe-like-api-for-lightning-c84762f4f634 Accept lightning payments easily with Strike] | ||
+ | *[https://medium.com/@JimmyMow/announcing-zap-beta-release-346b5100376e Announcing Zap beta release] | ||
[[Category:Cryptocurrency]] | [[Category:Cryptocurrency]] |
Revision as of 12:33, 28 January 2018
The Lightning Network represents an improvement in efficiency and uses a more logical payment network structure. Instead of broadcasting a transaction to everyone, the transaction can be sent more directly to the payment recipient. Only when parties to the transaction are dishonest, does one need to resort to the cumbersome process, which distributed censorship-resistant systems require to maintain consensus. In this way, one can achieve performance and efficiency almost equivalent to that of direct communication between the parties over the Internet, while retaining some of the security characteristics of Bitcoin’s blockchain.
See also
- About the lightning network
- Run your own mainnet lightning node
- Lightning-charge - a drop-in solution for accepting lightning payments
- How privacy will be done with Lightning
- Accept lightning payments easily with Strike
- Announcing Zap beta release