Bitcoin Lightning Network Node


Capacity: 47,114,151 SAT (~0.471 BTC)
Channels: 13
TOR Lightning Address

13 channels
Updated 28 days ago
Capacity (SAT)
Last seen 15 days ago · Joined 3 months ago , c-lightning







Ratings Received:

Possible current attack on lightning network. Node temporarily offline to await information and patch.

Posted 15 days ago

Some of my channels have closed outside of my doing. I suspect this to be some sort of attack, or exploit being actively tested. My lightning node is temporarily stopped until the patch for clightning is ready. If you had a channel open with me that closed, we can reestablish them. If you currently have a channel open to me, be patient, I will be back online in less than a week. I stopped the lightning router to prevent channel closures from this suspected attack. See this for details Posting here as a PSA and to gain attention to this issue I reported on github. If this is some sort of attack it could be disruptive to the lightning network at scale if not fixed immediately and cause on chain congestion. If anyone has information on what is going on in my scenario please share.

1 Reply

Dual funded channels, and a native decentralized liquidity market on the lightning network

Posted 27 days ago

My node InternationalRoutingService is offering liquidity and dual funded channels.

The latest version of C-Lightning version 0.10.1 it has a new functionality of dual funded channels and liquidity advertisements.

This requires at c-lightning verison 0.10.1 and the experimental dual fund option switched on. This can be enabled by setting the option experimental-dual-fund within your configuration file. Or you can pass the flag --experimental-dual-fund when starting clightning.

Dual funded channels
With dual funded channels, a single channel can be opened up between two nodes with funds contributed by both nodes enabling liquidity on both sides of the channel. This creates both inbound and outbound liquidity between two nodes on a single channel creation.

Liquidity market built into the lightning network
And now c-lightning nodes can also advertise liquidity offers directly within the lightning network. Any c-lightning node can offer liquidity and find other c-lightning nodes advertising liquidity. By default liquidity leases last for 4032 blocks, approximately 1 month.

When requesting inbound liquidity from a c-lightning node you can optionally dual fund it on your side also for a partially or fully balanced channel to compliment your inbound liquidity. Or else you can just request inbound capacity as long as you have enough funds in your wallet to pay for the lease.

At the time of this writing there are 9 nodes advertising liquidity on the lightning network using this feature. You can search for nodes offering liquidity and their rates with the command 
lightning-cli listnodes | grep -B20 -A7 option_will_fund

You can view the information for a specific node using the listnodes command which also contains information on liquidity offers. For example, to get information on my node you would type the command  
lightning-cli listnodes 03a7c61c056023c804c6d63693345e00ed8e2b28c8d2e0c455964bfff31128df40

I am charging 0 fees on channels in opened through this offer. And charging 60 basis points 0.6% on inbound liquidity. For example if a node is requesting 5,000,000 sats of inbound liquidity my node would charge 30,000 sats when the channel is opened. Right now my node is earning sats on leasing liquidity instead of transaction fees. At the moment most or all of my channels have zero fees.

My node is a tor only node. At some point I plan to get a clearnet proxy for it. If your node has tor installed you can connect to nodes both on the clearnet or tor. If you do not have tor, a tor node has to first connect to you.

To connect to my node and request inbound liquidity you can use the following two commands. You will want to adjust the variables amount= and request_amt= in the second command. amount= is how much you are funding on your side of the channel. request_amt= is how much inbound capacity you are requesting to be leased. The "compact_lease" in this example is accurate at the time of this writing. If this command does not work you will want to check for the latest compact_lease ID. You can find the current compact_lease ID with the listnodes command mentioned earlier.

lightning-cli connect 03a7c61c056023c804c6d63693345e00ed8e2b28c8d2e0c455964bfff31128df40@h7a7yk4jixep6ozr7u2ehurh33kbznffzd4b5dsz7evoupexdh26lgqd.onion:9735

lightning-cli fundchannel -k id=03a7c61c056023c804c6d63693345e00ed8e2b28c8d2e0c455964bfff31128df40 amount=0sat request_amt=50000000sat compact_lease=029a003c000000000001

More information

1 Reply

Participating in 3 Swaps

Triangle Capacity: 4,000,000 SAT

View Swap ID: 1049

Triangle Capacity: 2,000,000 SAT

View Swap ID: 1047

Triangle Capacity: 2,000,000 SAT

View Swap ID: 849


This bitcoin lightning network node identified by the pubkey: 03a7c61c056023c804c6d63693345e00ed8e2b28c8d2e0c455964bfff31128df40 also known by the alias: InternationalRoutingService is accessible on the lightning network address: 03a7c61c056023c804c6d63693345e00ed8e2b28c8d2e0c455964bfff31128df40@h7a7yk4jixep6ozr7u2ehurh33kbznffzd4b5dsz7evoupexdh26lgqd.onion:9735 .

The node has 13 channels, and a total channel capacity of: 47,114,151 Satoshis, which is equivalent to ~0.471 BTC. The node's physical location and IP address is protected by the TOR network to preserve privacy. The node's hex color is #ffa500. The information regarding this node and it channels has been updated last on 2021-10-23 12:22:49 UTC.

This node page has been claimed by user: InternationalRoutingService and has been verified through a digital signature as well. The user has created their account 3 months ago, and has been last seen 15 days ago.

The user has participated in 3 swaps on LightningNetwork+. The node operator has opened 3 channels to LN+ users through Swaps. The user has received 3 positive ratings from other users. The user has generously donated to LN+ to support the operation of the site.

To learn more about this node, including historical data visit the following lightning network node explorers.