Skip to content
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

Closed
rootzoll opened this issue Mar 4, 2019 · 11 comments
Closed

INFO: How to get Channel Liquidity fast? #395

rootzoll opened this issue Mar 4, 2019 · 11 comments

Comments

@rootzoll
Copy link
Collaborator

rootzoll commented Mar 4, 2019

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

@rootzoll
Copy link
Collaborator Author

rootzoll commented Mar 4, 2019

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.

https://github.com/shocknet/singles-api

@rootzoll
Copy link
Collaborator Author

rootzoll commented Mar 4, 2019

Thor: Lightning Channel-Opening Service
Buy incomming capacity - by Bitrefill.

https://www.bitrefill.com/thor-lightning-network-channels

@rootzoll
Copy link
Collaborator Author

rootzoll commented Mar 4, 2019

lightningto.me will provide you with a 0.02 BTC incomming bandwidth to get started.
You need at least have 10 channels open to use this service.

https://lightningto.me

@rootzoll
Copy link
Collaborator Author

rootzoll commented Mar 4, 2019

lightninghood.com - buy incomming capacity, also for TOR nodes

https://lightninghood.com/lightning-hood-liquidity/

@rootzoll
Copy link
Collaborator Author

rootzoll commented Mar 4, 2019

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.

https://lightningpowerusers.com/home/

@vmavromatis
Copy link
Contributor

Need an inbound channel? $3.54 USD for 2m sat

https://yalls.org/about/

@rootzoll
Copy link
Collaborator Author

rootzoll commented Mar 4, 2019

Also just showed up on open bazzar:
Lightning Network Inbound Channel for Liquidity

https://openbazaar.com/store/QmQbk7yu9RGiAv3eM3B92AW4pTNeM5rPGhLaQTf3u9GKCK/lightning-network-inbound-channel-for-liquidity

@openoms
Copy link
Collaborator

openoms commented May 22, 2019

Aiming to update this with anything significant, comments and PR-s are also welcome: https://github.com/openoms/lightning-node-management

@thephizzz
Copy link

I have a real noobie question about balancing. I have two channels - both to the same PubKey, different channel ID - one with a local balance and no remote balance and the other with a remote balance and no local.
Is this a correct balancing? Or does it need to be on only one channel?
See picture>
Thanks.
RTL Balancing

@rootzoll
Copy link
Collaborator Author

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.

@rootzoll rootzoll reopened this Nov 16, 2019
@openoms
Copy link
Collaborator

openoms commented Nov 8, 2021

closing this due to inactivity.
See a more up-to-date list: https://github.com/openoms/lightning-node-management/blob/en/createinboundliquidity.md

@openoms openoms closed this as completed Nov 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants