100.0M SAT / 1.0 BTC
All 3 spaces are filled
12 months or more
Open at least till: September 24, 2022
As reported in your profile, which updates every hour.
Minimum number of channels
Minimum total channel capacity
This is a Bitcoin Lightning Network liquidity swap, designed to help LN node operators generate both outgoing and incoming liquidity, increase connectivity and decentralization of the network.
Swap ID: 2509 was created on September 17, 2021 by LND ⚡ Routing.
What to Do Next?
This Swap is closed for applications. Please find another Swap, and sign in to join or start a new one.
Applied 3 months ago and last seen 27 days ago.
Has ~98.518 BTC capacity in 254 channels.
Rank: 10 / Iridium Node.
A have opened to B
Applied 3 months ago and last seen 1 day ago.
Has ~33.013 BTC capacity in 311 channels.
Rank: 10 / Iridium Node.
B have opened to C
Applied 2 months ago and last seen 2 months ago.
Has ~16.389 BTC capacity in 72 channels.
C have opened to A
LNDRouting - I have a small 5m Channel with you. Medium, I have a 10m channel with you. Happy to remove these if we go ahead on this one - Would you be ok with that guys? Node Layercake...
lets do it...
Yes, no problem. Channel opened.
Excellent triangle this!
ive closed the smaller ones just for easier admin ...
It's up to you guys if you want to close the smaller ones or not.
We developed a preprocessor for charge-lnd to manage multiple channels with the same peer in case it's useful for anyone else.
that is very cool - thank you for sharing - for me, i just want to scale up with channels - singular, rather than multiple - just seems easier for me, but totally get the product...
How about a Loop out product that is solid? and we can all use !! Then im very interested.. haha
Offering a loop out product is challenging for the same reason loop is unreliable. We don't want to drain all of our hard earned inbound liquidity.
Loop ins would be easy, but demand seems lacking.
Wow - ok, didnt realize you were tied in with the whole LND thing - silly me - why have I been booted from connecting to LOOP? What's that all about? Do you have any idea why 2 of my channels would be removed from LOOP? Bizarre..
We are not associated with anything but our own node and service.
LOOP does close channels regularly once all the liquidity is on their side though. It's how their service works, they need to close channels in order to get the bitcoins out and send them on chain.
Having channels to the LOOP node can be profitable if managed correctly, but just randomly opening to them will drain all of your inbound.
thanks for your help...
Hey LND-ROUTING. Thanks again for the heads up on the perils of opening a channel with LOOP. Just an fyi, I was closed on 2 channels - Both were co-operative closes - 1 - was a 200m channel and I had 63m left on that - And the 2nd was a 150m Channel, which I had 27m left in that. So, I guess there must of been quite a demand which required my channels to be closed. FYI, I have opened a fresh 200m channel for October.. We can see how that performs.. Of course, its not related to your Channel or business, I appreciate. Just good to timestamp this, as its a bit weird, dont you think? Thanks again...
medium_of_exchange wrote 2 months ago
hey LND Routing, I'm having trouble staying connected to your node, are you guys down?
LND ⚡ Routing wrote about 2 months ago
Had some issues with our tor daemon overloading last week or so. Still unsure of what the exact cause is, possibly some kind of DoS, but we greatly increased the resource allocation and it seems to be resolved for now.
medium_of_exchange wrote 5 days ago
LND ⚡ Routing - unable to connect again. over clearnet I get this:
[lncli] rpc error: code = Unknown desc = read tcp 220.127.116.11:36990->18.104.22.168:9735: i/o timeout
are you able to connect to my node?
Please sign in to post comments.