Difference between revisions of "Main Page"
MiltonPusser (talk | contribs) (BEtter definition) |
MiltonPusser (talk | contribs) |
||
Line 8: | Line 8: | ||
[[Channels|Payment channels]] are trust-minimized, since any attempt to [[Fraud|defraud]] the current agreed-upon balance in the channel results in the complete forfeiture of funds by the liable party. | [[Channels|Payment channels]] are trust-minimized, since any attempt to [[Fraud|defraud]] the current agreed-upon balance in the channel results in the complete forfeiture of funds by the liable party. | ||
By moving payments off-chain, the cost of opening and closing channels (in the form of [[On-chain transactions|on-chain]] transaction fees) is ammortized over the volume of payments in that channel, enabling [[Payment|micropayments]] and small-value transactions for which the [[On-chain transactions|on-chain]] transaction fees would otherwise be too expensive to justify. Furthermore, the Lightning Network scales not with the transaction throughput of the underlying blockchain, but with modern data processing and latency limits - payments can be made nearly as quickly as packets can be sent. | By moving payments off-chain, the cost of opening and closing channels (in the form of [[On-chain transactions|on-chain]] transaction fees) is ammortized over the volume of payments in that channel, enabling [[Payment|micropayments]] and small-value transactions for which the [[On-chain transactions|on-chain]] transaction fees would otherwise be too expensive to justify. Furthermore, the Lightning Network scales not with the transaction throughput of the underlying blockchain, but with modern data processing and latency limits - payments can be made nearly as quickly as packets can be sent. All of this with low [[Fees]]. | ||
[[Hash Time-Locked Contracts]] (HTLCs) allow transactions to be sent between parties who do not have a direct channels by routing it through multiple hops, so anyone connected to the Lightning Network is part of a single, interconnected global financial system. | [[Hash Time-Locked Contracts]] (HTLCs) allow transactions to be sent between parties who do not have a direct channels by routing it through multiple hops, so anyone connected to the Lightning Network is part of a single, interconnected global financial system. |
Revision as of 07:54, 17 January 2019
Thunderbolts and lightning, very very... exciting!
The Lightning Network scales blockchains and enables trust-minimized instant payments by keeping most transactions off-chain and leveraging the security of the underlying blockchain as an arbitration layer. This is accomplished primarily through "payment-channels”, wherein two parties commit funds and pay each other by updating the balance redeemable by either party in the channel. This process is instant and saves users from having to wait for block confirmations before they can render goods or services. Payment channels are trust-minimized, since any attempt to defraud the current agreed-upon balance in the channel results in the complete forfeiture of funds by the liable party. By moving payments off-chain, the cost of opening and closing channels (in the form of on-chain transaction fees) is ammortized over the volume of payments in that channel, enabling micropayments and small-value transactions for which the on-chain transaction fees would otherwise be too expensive to justify. Furthermore, the Lightning Network scales not with the transaction throughput of the underlying blockchain, but with modern data processing and latency limits - payments can be made nearly as quickly as packets can be sent. All of this with low Fees. Hash Time-Locked Contracts (HTLCs) allow transactions to be sent between parties who do not have a direct channels by routing it through multiple hops, so anyone connected to the Lightning Network is part of a single, interconnected global financial system. In short, the Lightning Network enables scalable blockchains through a high-volume of instant transactions not requiring custodial delegation.
|
Read (or write) about How Lightning Works, Nodes, Invoices, Channels, Wallets, Services, shops or read information on editing the wiki. For questions use the contact form on Wiki contact.
|
All pages
Please help by expanding this wiki
- ACINQ
- AMP
- Alternatives
- Atomic swap
- Autopilot
- BOLT
- BOLT 1
- BOLT 10
- BOLT 10: DNS Bootstrap and Assisted Node Location
- BOLT 11
- BOLT 11: Invoice Protocol for Lightning Payments
- BOLT 1: Base Protocol
- BOLT 2
- BOLT 2: Peer Protocol for Channel Management
- BOLT 3
- BOLT 3: Bitcoin Transaction and Script Formats
- BOLT 4
- BOLT 4: Onion Routing Protocol
- BOLT 5
- BOLT 5: Recommendations for On-chain Transaction Handling
- BOLT 6
- BOLT 7
- BOLT 7: P2P Node and Channel Discovery
- BOLT 8
- BOLT 8: Encrypted and Authenticated Transport
- BOLT 9
- BOLT 9: Assigned Feature Flags
- BOLTs
- BOS Score
- Backup
- Balancing channels
- Benefits
- Bitcoin
- Bitcoin Mainnet vs Testnet
- Bitcoin in El Salvador
- Blockstream
- Bos score
- Bumping fee for lightning channel open
- C-lightning
- Change fees
- Changing fees
- Channel
- ChannelReserve
- Channel Factory
- Channel balance
- Channel capacity
- Channel graph
- Channel policy
- Channels
- Charging With Lightning
- Chat about Lightning
- Check routing on LND
- Closing Transaction
- Closing channels
- Closing transaction
- Commitment Transaction
- Como Funciona A Amarração Amorosa
- Competition
- Cross-chain
- Cross-chain transactions
- Custodial
- Dangers
- Data loss protection
- Debug
- Debugging LND
- Delays
- Denominations
- Dual Funded Channels
- Eclair
- Eclair Mobile
- Editing the wiki
- Eltoo
- Exchanges
- Exchanges using lightning
- Explorers
- FAQ
- Fees
- Fraud
- Funding Transaction
- Future
- Gossiping
- Graph
- HODL HLTC
- HODL Invoice
- HOWTO
- HTLC
- Hardware
- Hash Time-Locked Contracts
- History
- How Lightning Works
- How to add your node to the node list
- Incoming liquidity
- Incoming liquidity requests
- Invoice
- Key send
- Keys
- Keys and backups
- LND
- LND checksum mismatch
- LNDash
- Layer
- Layer-1
- Layer-2
- Layer-3
- Layers
- Libraries
- LightningFlip
- Lightning Labs
- Lightning Network
- Lightning Network explorers
- Lightning Onion Routing
- Lightning Pool
- Lightning Rendezvous Routing
- Lightning Torch
- Lightning network paper
- Lightning node
- Lightning nodes
- Liquidity
- Lit
- Litecoin
- Litego.io
- Lnd
- Lnd memory issues and OOM
- Logo
- Loop
- Mailing Lists
- Main Page
- Mainnet
- Making money using Lightning
- Meetups
- Meetups and events
- Millisatoshis
- Mobile apps
- Msat
- Multiple channels not supported
- Multisig
- Network
- Neutrino
- No route error
- Node
- Node/1ml
- Node/ACINQ
- Node/BenFranklin
- Node/ConsensusNetworksBolt
- Node/LN-MasterNode
- Node/LNBig
- Node/PEBERG
- Node/lnd02.beckorg.com
- Node Management
- Nodes
- Non-custodial
- On-chain
- On-chain transactions
- Onion Routing
- Opening channels
- Pay to self
- Payment
- Payment providers
- Payments
- Payments provider
- Podcasts
- Poke
- Privacy
- Probing
- Products
- Punishing Transaction
- Q&A
- Quick Start
- RPC auth for bitcoind
- RTL
- R hash
- Raspiblitz
- Rebalance-lnd
- Resources
- Reviving channels
- Rewards
- Risks
- Route
- Routing
- Rust Lightning
- Sandbox
- Sat
- Satoshi
- Satoshi's Vision
- Scaling
- Seed
- Services
- Setting alias and color for Umbrel
- Setting alias for Umbrel
- Setting up a LND node
- Setting up a Lightning node
- Shops accepting Lightning Payments
- Shops and services accepting Lightning Payments
- Side-chain
- Sphinx
- Splicing
- Spontaneous payment
- Stakenet
- Static channel backups
- Submarine Swaps
- TOR node at home, cloud IP
- Testnet
- Tor
- Trampoline
- Transaction
- Turbo Channels
- Umbrel
- Unilateral (permissionless) payments
- Using Autopilot on LND
- Videos
- Wallet
- Wallet Of Satoshi
- Wallets
- Watchtower
- Watchtowers
- Wiki Torch
- Wiki contact
- Wumbo