pull down to refresh
33 sats \ 3 replies \ @ambosstech 26 Jun \ parent \ on: Sold my first Magma channel yesterday... Highly Recommended! lightning
This is a lot of FUD to unpack!
We aren't creating fake orders on Magma; it pays out Bitcoin to sellers and that's simply not something we can afford as a small startup.
Hydro does not require sharing any channel information; it's simply a liquidity automation service for sovereign node operators. It could have just been called Auto Magma. The automation works best when there's liquidity information to inform channel opens, but that's optional and a conscious user choice.
Our ML research is used to inform better pathfinding and higher performance for lightning, just like giving better driving directions by using traffic data. Our predictions are not useful for exposing anything that is private; it's simply a more scalable tech than probing, which is invasive and damaging to network performance.
Why does Hydro need to send ANY data to Amboss? Why can't everything run locally on the node?
More scalable probing == Less privacy for everyone
Maybe there's a reason current probing is damaging to performance.
reply
Local automation is already an available service through CLBOSS and LNDg. However, making good decisions about whom to connect to is stymied by only using data local to the node. This optimization problem is a better fit to centralized processing as we see with Waze/google/Amazon.
The only Hydro setting that requires data is inbound liquidity targets. Setting target inbound liquidity automations requires attesting to the current inbound liquidity, but it's just an attestation.
reply
Local automation is already an available service through CLBOSS and LNDg
Just because nobody else was collecting data. Does not give excuse for someone to start collecting data.
Making good decisions about whom to connect to is [difficult]
No, its easy. Just open channels to who you need to pay the most. This strategy works amazing for pleb, business, and exchange nodes.
What's difficult is what you're trying to do: making good decisions FOR OTHER NODES about whom to connect to.
Making good decisions for others requires knowing more about them than they do. This is anti-privacy by definition.
reply