Comment on page
Routing
Aimed for forwading payments successfully while generating profit.
- high
- connect to the network edge to get usage
- aim to connect node clusters (isolated groups)
- balanced between local and remote overall
- individual channels should be able to forward payments in both directions
- aim to be perfect
- offline routing nodes with many public channels are causing networkwide payment failures
- autorebalancing (cronjobs are useful)
- create inbound and outbound liquidity as required
- balance between multiple nodes
- close inactive channels
- open to directions where liquidity is required
- use Lightning Pool, Amboss Magma or liquidity ads bids and asks
- batch channel opens to save on miner fees
- fund channels from external wallets
- close to external addresses to reduce the hot wallet risk
- bidirectional traffic
- fees are low
- highly competitive (lots of liquidity is in private channels)
- high incoming liquidity required
- fees can be set to moderate - high
- selling channels via Lightning Pool often falls into this category
- fees can be left to be low
- traffic is mostly outgoing
- should encourage the usage of private channels
- offline public channels lead to payment failures and affecting the routing node's reputation)
- Custom system on enterprise hardware focused on uptime and redundancy
- Hosted on a VPS (higher risk)
Last modified 1yr ago