All Projects → lnd-routing → lnd-routing

lnd-routing / lnd-routing

Licence: other
Lightning network liquidity service

Programming Languages

python
139335 projects - #7 most used programming language

Projects that are alternatives of or similar to lnd-routing

Eclair Mobile
An Android wallet for the Lightning Network
Stars: ✭ 231 (+1343.75%)
Mutual labels:  lightning, payments, lightning-network
Lnd
Lightning Network Daemon ⚡️
Stars: ✭ 5,623 (+35043.75%)
Mutual labels:  lightning, payments, lightning-network
Eclair
A scala implementation of the Lightning Network.
Stars: ✭ 892 (+5475%)
Mutual labels:  lightning, payments, lightning-network
lightning-qt
bitcoin-qt for lightningd
Stars: ✭ 36 (+125%)
Mutual labels:  lightning, lightning-network
Lncli Web
Light-weight web client for the lnd daemon written in NodeJS / Angular.
Stars: ✭ 181 (+1031.25%)
Mutual labels:  lightning, lightning-network
Ln Service
Node.js interface to LND
Stars: ✭ 191 (+1093.75%)
Mutual labels:  lightning, lightning-network
Umbrel Os
Run Umbrel Bitcoin and Lightning node on a Raspberry Pi in one click
Stars: ✭ 132 (+725%)
Mutual labels:  lightning, lightning-network
lntop
⚡ LN terminal dashboard 📊
Stars: ✭ 170 (+962.5%)
Mutual labels:  lightning, lightning-network
Spark Wallet
⚡️ A minimalistic wallet GUI for c-lightning, accessible over the web or through mobile and desktop apps.
Stars: ✭ 215 (+1243.75%)
Mutual labels:  lightning, lightning-network
umbrel-middleware
RESTful Bitcoin and Lightning API for Umbrel
Stars: ✭ 21 (+31.25%)
Mutual labels:  lightning, lightning-network
lightning-jet
Lightning Jet is a fully automated rebalancer for Lightning nodes. Jet optimizes channel liquidity allocation based on routing volume, missed routing opportunities (htlcs), and other variables.
Stars: ✭ 33 (+106.25%)
Mutual labels:  lightning, lightning-network
Zeus
A mobile Bitcoin/Lightning app for lnd, c-lightning, and Eclair node operators ⚡️
Stars: ✭ 175 (+993.75%)
Mutual labels:  lightning, lightning-network
Webln
Spec and client library for WebLN apps and providers
Stars: ✭ 165 (+931.25%)
Mutual labels:  lightning, lightning-network
Lndhub
Wrapper for Lightning Network Daemon. It provides separate accounts and trust minimization for end users
Stars: ✭ 203 (+1168.75%)
Mutual labels:  lightning, lightning-network
Paper
Lightning Network Paper
Stars: ✭ 136 (+750%)
Mutual labels:  lightning, lightning-network
lightningtip
Get tips via the Lightning Network
Stars: ✭ 91 (+468.75%)
Mutual labels:  lightning, lightning-network
lnregtest
Regtest Lightning Networks for (python) integration testing
Stars: ✭ 17 (+6.25%)
Mutual labels:  lightning, lightning-network
pi-factory
Bootstrap a bitcoin lightning box for Raspberry Pi 3 based on Alpine Linux
Stars: ✭ 17 (+6.25%)
Mutual labels:  lightning, lightning-network
Phoenix
Phoenix is a non custodial Bitcoin wallet using Lightning to send/receive payments.
Stars: ✭ 129 (+706.25%)
Mutual labels:  lightning, lightning-network
Awesome Bitcoin Payment Processors
🌟 A curated list of Bitcoin payment processors enabling merchants, businesses and nonprofits to accept Bitcoin payments.
Stars: ✭ 129 (+706.25%)
Mutual labels:  lightning, lightning-network

LND Routing

High capacity, high availability, well connected, fast lightning node.

We aim to become a top liquidity provider for the lightning network.

  • Actively managed liquidity, virtually guaranteeing successful payments up to your channel size.
  • Large channels to popular destinations and major routing nodes.
  • Open channels to any node, for a friend, or to your favorite service provider.
  • Private LN-only interface via Tor, minimizing our attack surface and maintaining uptime.
  • Fast clustered servers for reliability.
  • Up to 1.5BTC channels, minimum 100k sats. Larger available on request with proven routing history.
  • Competitive pricing and fees.

Quick and easy

Use request_channel.py to request an incoming channel.

wget https://raw.githubusercontent.com/lnd-routing/lnd-routing/master/request_channel.py
python3 request_channel.py

Channel open requests

We have developed a keysend based protocol for paid channel requests. It is based on the keysend messaging protocol.

To request a channel opening, send us a keysend of (desired_channel_value * 0.0025) + 500 sats with custom records 1667785070=01 (for a public channel) or 1667785070=02 (for a private channel) and 34349339=<node_pubkey>. You can optionally include a message in record 34349334 as a hex encoded UTF-8 string. Our node will attempt to connect to yours and open a channel within a few seconds.

  • Minimum channel size is 100,000 sats.
  • Maxmimum channel size is 1.5 btc.
  • Channels remain open as long as they are active.
  • Minimum 1 month of inactivity before closing, only if liquidity is needed elsewhere.

Automatic refunds for failed channel openings are issued via keysend to the specified node.

Please check your data carefully, refunds are only automatically issued for failed channel openings, not invalid inputs. We highly suggest using request_channel.py.

Our node will attempt to look up and connect to yours, but for best results, connect to us as a peer prior to requesting a channel.

lncli connect 02ab583d430015f3b6b41730434b5fac264901b50199f0b9becc0a98a365f581a9@lndroutekytme3xds6cmbxaniretdgox2hk4cpu4k27jnub3gkfeuhqd.onion:9735

lightning-cli connect 02ab583d430015f3b6b41730434b5fac264901b50199f0b9becc0a98a365f581a9@lndroutekytme3xds6cmbxaniretdgox2hk4cpu4k27jnub3gkfeuhqd.onion:9735

eclair-cli connect --uri=02ab583d430015f3b6b41730434b5fac264901b50199f0b9becc0a98a365f581a9@lndroutekytme3xds6cmbxaniretdgox2hk4cpu4k27jnub3gkfeuhqd.onion:9735

A clearnet proxy is now avaliable using 02ab583d430015f3b6b41730434b5fac264901b50199f0b9becc0a98a365f581a9@139.59.142.221:9735

We currently only have instructions for paying for channel requests from LND, but the destination node can be running any implementation.

Template:

Replace the parts containing brackets. We have received several channel requests to the non-existant example nodes.

lncli sendpayment --keysend  --amt <(desired_channel_value * 0.0025) + 500> \
--dest 02ab583d430015f3b6b41730434b5fac264901b50199f0b9becc0a98a365f581a9 \
--data 1667785070=01,34349339=<your_node_pubkey>

Please make sure you edit the examples before using. We are still getting invalid requests. From our logs:

Received channel open request to 0102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f2021, received: 250500sat
Attempting to connect to peer: 0102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f2021
Error getting node info: 0102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f2021
Error sending refund to 0102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f2021 of 250500sat: no_route

Examples:

To request a 0.1btc public channel from us to node 0102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f2021:

lncli sendpayment --keysend  --amt 25500 \
--dest 02ab583d430015f3b6b41730434b5fac264901b50199f0b9becc0a98a365f581a9 \
--data 1667785070=01,34349339=0102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f2021

To request a 0.1btc private channel from us to node 0102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f2021:

lncli sendpayment --keysend  --amt 25500 \
--dest 02ab583d430015f3b6b41730434b5fac264901b50199f0b9becc0a98a365f581a9 \
--data 1667785070=02,34349339=0102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f2021

To request a 0.2btc public channel from us to node 22232425262728292a2b2c2d2e2f303132333435363738393a3b3c3d3e3f404142 with "Hello LND.Routing" as a message to us:

lncli sendpayment --keysend --amt 50500 \
--dest 02ab583d430015f3b6b41730434b5fac264901b50199f0b9becc0a98a365f581a9 \
--data 1667785070=01,34349339=22232425262728292a2b2c2d2e2f303132333435363738393a3b3c3d3e3f404142,34349334=48656c6c6f204c4e442e526f7574696e67`

To simply send us a message:

lncli sendpayment --keysend --amt 1 \
--dest 02ab583d430015f3b6b41730434b5fac264901b50199f0b9becc0a98a365f581a9 \
--data 34349334=48656c6c6f204c4e442e526f7574696e67`

If you have any issues, open one on this repo.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].