pull down to refresh
135 sats \ 3 replies \ @SimpleStacker 27 Mar \ on: Hydrus - Automating lightning liquidity management lightning
Hmm, very interesting. I'm always happy to see people work on LN development. I'm an amateur LN node runner, but I've never been able to do so profitably. Nor do I have any intention of spending the time to make it profitable, but if someone can make an easy to install software that automates it, I'd be very interested.
Questions:
How often does it decide to open/close channels and how does it decide when is a good time? I assume it looks at on-chain fees, but what's the decision rule?
You also mentioned centrality vs channel fees in determining which nodes to open channels to. But I thought channel fees were not public info? Maybe I'm wrong about that
You also mentioned centrality vs channel fees in determining which nodes to open channels to. But I thought channel fees were not public info?
Routing policies are public, otherwise your node wouldn't be able to construct a route. You get all the network nodes routing policies using the
lncli describegraph command, it will display all edges and two fields node1_policy and node2_policy indicating how much fees they charge, HTLC ranges, etc.reply
thanks, good to know!
reply
How often does it decide to open/close channels and how does it decide when is a good time? I assume it looks at on-chain fees, but what's the decision rule?
That is up to the user to decide, you can run Hydrus daily, once a week, once a month, etc. This is typically configured in the systemd service timer or in a cronjob.
Once executed, the agent gathers information from the local node to decide whether it should open new channels (num_channels < max_channels) or potentially close some (num_channels > min_channels). So in some scenarios it may not do any changes.
Apart from that, there's a configuration called
agent.channel_manager.max_sat_vb which is the maximum number of satoshis per virtual byte that you are willing to spend. If transaction fee is estimated to be higher than that value, no changes will be made.So yeah, the agent can be scheduled to execute at anytime but it may do nothing depending on certain factors.
reply