C_Otto

~hyperlinks

tech

AskSN

Linux users of SN: What distro you running? Are you a "ricer"?

nichro

Around 24 years of Debian for me. Once it starts to annoy me, I might start looking for something else. I'm not in a rush, though.

Target of auto withdrawal

OK, reset helps. I guess the concept changed without me getting a passphrase.

This shows me an "unlock wallets" button ("your passphrase is required"). I don't have a passphrase, and I don't think I created a wallet in stacker.news.

I configured autowithdrawal, which works: I see sats in my wallet. However, I don't see where I configured the destination address, or where I could change it. Could you please point me to this setting? Thanks!

bitcoin

@C_Otto's bio

Hi, I don't think my website is offline. The liquidity decrease is due to peers closing channels, after lots of activity. It's part of the game.

lightning

My 1 month pleb Lightning Node update

NEEDcreations

How much did you pay for onchain transactions?

As a continuation of https://stacker.news/items/1069842/r/C_Otto, I wonder what's going on with bfx-lnd0. The youngest (most recently opened) channel is 67 days old, as seen on https://amboss.space/node/033d8656219478701227199cbd6f670335c8d408a92ae88b962c49d4dc0e83e025?section=Channels.

I'd like to open a new channel to bfx-lnd0, but this isn't possible: "Number of pending channels exceed maximum"

Hitting the configured maximum isn't unlikely, but instead of this being a temporary fluke, it seems like Bitfinex actively disallows new channels. Why? Traffic towards bfx-lnd0 is still in high demand.

What's going on with bfx-lnd0?

Bitfinex' bfx-lnd1 node seems to be offline, with several force-closed channels. The channel with my node has been force-closed by their node, and I don't know why that happened. Do you know what's going on?

What's going on with bfx-lnd1?

Get in Line for SNZ 9

plebpoet

Who is 03e6871fe33c45df778f2adadb795ee838892e809ff8daaabf11053be4190c5be1?

This looks like a new big player to me. Lots of non-wumbo sized channels, which seem to be opened on demand, automatically (at least based on my personal observation on c-otto.de). The node is hosted in the cloud, and I don't see any contact information. Does anyone know more about this node?

https://amboss.space/node/03e6871fe33c45df778f2adadb795ee838892e809ff8daaabf11053be4190c5be1

Lightning Network : our high-maintenance crazy-ex

avbpod

Parallel channels are a mess - a rant

Interesting. Can you point to where this is described in the spec?

Two or more lightning network channels connecting the same pair of nodes.

I spent the day understanding and fixing a bug in lnd-manageJ's payment system. Turns out, Nicehash has two nodes, and two channels between those nodes. One worth 5 BTC (https://amboss.space/edge/917695285539373056), one just 0.01 BTC (https://amboss.space/edge/915246673132126208). Quite the difference. To make things worse, the smaller channel is free, while the larger one charges 1ppm. Not so much of a difference, but still.

While running a "top up" payment (rebalancing using Pickhardt payments), the larger channel was used first (because of the size it's deemed better than the smaller channel, despite the costs). My code learned that some decent amount is available on that channel, due to a failure further down the line. This information was then also propagated to the other, smaller, channel. In subsequent attempts, both channels were used: the smaller channel up to the maximum, the larger channel for the remainder. Sadly, the smaller channel actually was rather empty, which confused my code into running in circles.

After understanding this issue, I took the channel ID into account when storing and using this kind of liquidity information. This way, the larger channel and the smaller channel are treated individually, which seems good at first glance (and actually worked as expected, as far as I know).

However, with parallel channels between two nodes (at least when they share their fee settings), the forwarding lightning network server is free to pick any of these parallel channels. As such, if I request a route via channel ID 123, the actual channel used might be one with ID 456. This unexpected ID is also returned in failure responses, messing up the code I just "fixed".

In the end, I think I'm better off leaving the code "as is". Which means: combining the information I have about parallel channels. Which also means: routing between the two Nicehash nodes won't really work. Similar issues might exist for other nodes that have parallel channels with different fee settings.

https://github.com/C-Otto/lnd-manageJ/

Routing Node History | SNL #165

Coinsreporter

I'm not "zero fee routing". The name change was an April fools joke.

My name's Marko, Software Developer at Primal

Marko

How do you know about my backup strategy? I'd say it's rather safe, but it's not connected to Primal nor my browser in any way. Please don't assume that I'm doing anything wrong. And if you do, please give me the option to acknowledge your warning once and for all.

Greetings! Could you please remove the constantly showing "1" badges? Thanks :)

![](https://m.stacker.news/84290)

![](https://m.stacker.news/84291)

Sometimes also on "Premium".

I guess I should not complain about a free service, though.

Smallest Routing fee ever for me!

siggy47

The LN internally uses 1/1000th of a sat, but when you close a channel, you only get full sats. Having lots of micropayments (or fees) worth <1sat can add up, though.