I agree with that. Use private channels if you don't mind to route , and keep well working your node. However I'm corious what are the main failures that disrupt the network . hardware failures? Disrupted network connection ? Unbalanced channels?
I am tired of people running shity nodes on RPi. They are stubborn in not want to understand that their shity node crashing could affect the whole network.
When these people will learn that they can still run a PRIVATE node (with unannounced channels), that are enough to pay the beer/coffee over LN.
https://stacker.news/items/402904?commentId=402941
FFS throw that RPi node to the fucking garbage!
When people will understand that the weak point for RPi nodes is the DC card and the USB cable that is literally fucking the data drive?
BTC and LN require a huge traffic I/O for both SD card and the data drive (no matter you use SSD or HDD). The simple fact that the drive is NOT internal is fucking this I/O traffic. And your node always get fucked.
If you want to run a PUBLIC ROUTING node, then get a fucking SERIOUS machine, with INTERNAL drives and in RAID. Also have 100% good maintenance and a lot of liquidity.
FFS stop running public nodes with less than 1BTC liquidity!
Discussion
Disruption examples?
Here is one example:
- I am paying a LN invoice to X destination.
- I am running a private node
- My payment went from my LSP/other private peers to a public node 2nd hop then to the 3rd hop, a RPi shity node that went offline for various reasons.
- that HTLC get stuck for several days until my channel will get force closed.
And was not even my fault, was just a random shity RPi node in the network.
So ... I think that for this nodes network stability could it be the major issue? It would be interesting to understand if the network protocol used it is strong enough and if it recover after failures .. I have to say that using umbrel under onion with odroid m1 and nvme storage, with lnd it always worked well .. No routing node ..
lightning's source routing system is brittle like this, and it's difficult to even gather useful data about the network, as well as propagate it effectively to mitigate this kind of fault
there's no doubt that there needs to be further development of the protocol
If more noobs will understand that is NOT really necessary that everybody should be a "public routing node", the network will be much better as it is today.
Most of force closing channels happen EXACTLY because of these shity nodes. And if we can limit to minimum necessary the force closed channels, LN will work quite well.
Having a LN structure by levels and users choose their own level based on their own capacity, will make things to go smooth and well.
High level: big routing nodes, professional ones, well maintained, huge liquidity. Providing high availability and liquidity for big routes.
Medium level: LSPs, well connected to the high level, providing liquidity and routes for private nodes and users.
Low level: edge nodes, private nodes, mobile private nodes, regular users.
But nooo, every noob now want to run a routing node with a shity RPi over Tor, "to earn sats and help the network", when in fact are only clogging the network.
i don't think #lightningnetwork is the final destination for L2s
i haven't looked deeply into Ark but my first impression is kinda favourable
i think that the problem we face is how to do trustless relaying of messages across the network that don't involve falsified UTXOs and can fall back to alternative routes when a planned route fails
it's a cryptography problem, and i'm almost certain there is already a specialised hash function that exactly does what we need, just nobody has figured out that it can do this
you also rage against the AI, i hate that shit, and you know it operates by a specialised hash function right? the AI hash is called a "proximity hash" and it allows you to plot multiple paths through a graph that generate a valid structure that humans recognise (they are like human memories, in fact)
something very close to this will enable us to do trustless path routing and the days of stuck payments will be over, just like QUIC and other new reliable transports have ended (most of) the connection reset by peer problems
actually, just articulating that first point about failure resistance
already right now, if LN protocol had a notion of forking it could be literally like lightning and if it forks into a dead end it can step back one, two, three etc hops and try alternatives
the messages would be a lot bigger but they would have resistance
i started working on this idea with Indra last year, how to do forks, the https://github.com/indra-labs/indra repo has code for "forking" messages, that encode multiple routes for a packet so it can even duplicate across and iirc i even made a join message