-
Notifications
You must be signed in to change notification settings - Fork 524
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
INFO: How to get Channel Liquidity fast? #395
Comments
Lightning Singles is a directory service for channel liquidity matchmaking on the Bitcoin Lightning Network. Submit your node information and ask the community to connect. |
Thor: Lightning Channel-Opening Service |
lightningto.me will provide you with a 0.02 BTC incomming bandwidth to get started. |
lightninghood.com - buy incomming capacity, also for TOR nodes |
lightningpowerusers.com - Open a channel with https://lightningpowerusers.com/home/ and I will open one in your direction, so you have capacity to receive BTC on the LN. |
|
Also just showed up on open bazzar: |
Aiming to update this with anything significant, comments and PR-s are also welcome: https://github.com/openoms/lightning-node-management |
The idea of balancing is that a ONE channel with a another can route maximum into both directions ... this is then its 1/2 local and 1/2 remote. When you have TWO channels with the same other node to maximise into both directions your strategy looks best balanced to me. |
closing this due to inactivity. |
Now that people have their RaspiBlitz setup the question is how to get it connected well with good incomming channel liquidity?
Best of course is if you meet other lightning node operators and ask them to open a channel with you. Beside that groundwork - lets collect some info what other ways there are to get Channel Liquidity fast.
BEWARE: Those services listed here are just a collection what is out there - not saying its the best way or that services are safe to use. Use at your own risk. #dyor
The text was updated successfully, but these errors were encountered: