Lightning Network Routing Node

Nightfort

Public Key

03ea23e773775eb33004bf7d3431c61317cb1e969995e631e3349bd1ba7e5e33f8

Connectivity

I keep the node reachable via IPv4 and IPv6, as well as Tor. If possible, you should prefer the clearnet sockets as they have lower latency than Tor. The node is physically located near Zurich, Switzerland. It is connected to the internet with a 10 Gbit/s symmetrical fiber connection.

IPv4
212.51.140.228:9735
IPv6
[2a02:168:62a7::b1c]:9735
Tor
2bqiqoilhretmpqhqiyjeb2fs6coeo4iebvzaeq4k3myg5iyjdjs5wad.onion:9735

Policies

Peers

All peers are welcome, no matter the age and size.

Channel Visiblity

I accept both public and private channels.

Private channels are assumed to drain in only one direction. When the balance is all on my side and the channel has been inactive for an extended period of time, I will close it during a period of low BTC fees and reallocate the funds.

Channel Size

The node accepts channel sizes between 1,000,000 and 100,000,000.

I recommended size around 20,000,000. This keeps the channel sizes on my node balanced. Though you are welcome to open a smaller or larger channel, as your funds allow.

Fees

The base fee is always zero. Fee rates are being continuously adjusted to nudge the balance towards the median. The minimum fee is 1, maximum 4,181. When the channel balance is all on your side, negative inbound fees are set to encourage increasing my inbound liquidity.

Min/Max HTLC

The minimum HTLC is 1 (if the channel constraints allow). The maximum HTLC is dynamically set to match the outbound liquidity. This minimizes local routing failures and gives other nodes a better chance to find a working path through the Lightning Network.

Operation

Channel fees and Max HTLC are continuously being adjusted to match the policies outlined in the previous section. This is done via background jobs that observe the current state of the node, channels, and forwarded HTLCs. They then adjust the policies accordingly.

Peer Swap

When possible, I use PeerSwap to rebalance the channels. When the peer does not support PeerSwap, I attempt the traditional form of rebalancing by pushing sats through one channel and receive through another. That is however not very reliable and fails more often than it succeeds.

Contact me to have your node whitelisted so that you can participate in a peer swap. My contact details are below.

Hardware and Software

Intel N6005, 32GB RAM, 10G NIC, NVMe (in RAID1 configuration).

Lightning Network Daemon (lnd)in version 0.19.1-beta, with a local bitcoind backend. Software configuration managed by NixOS.

Contact

You can reach me via email at operator@nightfort.systems.

Links

View this node on the following Lightning Network explorers: