tl;dr nothing bad happened, i'll be back
The infra the node runs on was in very bad shape and I had low confidence in how secure it was. Recent CVE's taught me there are many unknown unknowns out there and I could not asses the risks anymore.
I was already considering shutting down my node for some time because of how much time running a node consumes and I was getting tired of all the worrying.
But after shutting down I pretty quickly realized that I enjoy LN too much and I miss running my node. So right now I'm redesigning and rebuilding things in a more secure way and I hope to open new channels soon.
One of the largest Lighthing nodes (cyberdyne.sh) shut down. A real tragedy... Learned much from this operator over the last couple of years. @silenzara what happened with the node? 😭😭😭
amboss.space/node/03a93b87bf…
I simplified my channel acceptance criteria a lot and updated my site with the new policies: cyberdyne.sh/
Now it's just a simple size range from 10M sats minimum up to a max of 500M sats (if your node is large enough, otherwise the max might be lower).
PSA: I have started using positive inbound fees on select channels.
Negative inbound fees have been around for almost a year and have proven themselves as a very useful tool to enable routing nodes to be more effective and make the network more reliable.
Positive inbound fees carry the same power, but they are not backward compatible with nodes that do not understand this new protocol. Using positive inbound fees can and will make the network less reliable for nodes that are not compatible, and for this reason, I have not taken this decision lightly. Still, after weighing all considerations, I think now is the time to start using them.
I will be utilizing the fees as a protective measure to improve reachability to my node. Fee management is hard, and many nodes struggle to find appropriate fees. I have exhausted all other options to address this issue, and inbound fees are all I have left besides closing down a bunch of channels with well-intentioned peers.
To my peers who are 'affected' by the fees: feel free to increase your fee toward me by the same amount as the inbound fee toward you. My fees will automatically adjust down to 0 once a healthy balance has been reached. If you think positive inbound fees are bad and want to close, no problem.
To all maintainers of node implementations that do not support inbound fees yet: please take this protocol upgrade serious. I know there are different ideas on how to approach inbound fees, but what we have now already just works. Please work toward compatibility.
10
358
I just want to clarify that the only information I shared was the total amount forwarded and total number of transactions for the month November of 2024.
I don't have the exact numbers anymore but I think it was around 370 BTC in 90k transactions.
Replying to @SDWouters
We used the same methodology for our estimates as in 2023, but instead of having data on 52% of public capacity, we now got up to 79.4%
A massive thank you to @acinq_co, @getAlby, @Bitfinex, @Breez_Tech, @blocks, @lnbig_com, @Kraken, @LQWDTech, @NiceHashMining, @okx, @silenzara, @SunnySarahNode, @THNDRGames, @WalletOfSatoshi for sharing data.
4
288
What is this stupid trend of disabling forwarding on nodes that have all fees set to 0/1 ppm? First lightspark and now also fedi and henwen.
These nodes seem to think their use cases are more important than the reliability of the broader LN they make use of.
1
7
275
If you run a large or active LN node, please disable channels or reject forwards for a short while (max 5 min) before you take the node down to restart or perform maintenance.
This allows for most pending htlc's to clear and will improve the LN experience for our users.
The sad thing about LN is that there are many nodes that are totally unmanaged (or only care about their own needs) and fail 99.9% of their forwards. By just existing they make LN worse.
My dynamic blacklist has over 200 nodes now, some of them should really know and do better.
LN pathfinding algorithm development shouldn’t just take the perspective of the payer, it should also think about how routing node incentives can be reshaped. 99% of the time pathfinding fails now are because of an incentive problem where liquidity failure is not disincentivized.
2
233
Ratio based fee policies only work as a precision tool. Use narrow bands and update only on settled balances. Define multiple configs and apply those to subsets of peers. Re-evaluate often.
Using it as a single one-size-fits-all solution is probably a bad idea for most nodes.
1
164
I'm sure @f2pool will do the right thing and return the lost funds to this lightning node runner.
Because of a configuration error in a package he used, his entire local channel balance was lost in transaction fees when the channels force closed.
This Post is from an account that no longer exists. Learn more
326
Looks like @lightspark needs to resort to cannibalizing their channel infra because they can't handle the deposit volume.
They should probably limit the daily deposit amounts.
4
8
1,479
I will be migrating my nodes to new hardware soon, probably July 2nd or 3rd. Expected downtime is a few hours.
Will post again when I take the nodes down and once they are back up again.
Silen Zara retweeted
Let‘s talk about @ambosstech‘s new product „Reflex“ and why you should close all channels to Amboss immediately.
Reflex is a product bringing OFAC compliance to LN Nodes, yet the product is advertised as increasing „Freedom“ for node runners - and freedom, according to Amboss, apparently means compliance with some of the most unjust, racist regulations existing in the world today.
OFAC enforces trade sanctions based on US foreign policy and national security interests. These include financially interacting with *any* individuals from countries such as Russia, Iran, Cuba, Venezuela, or Syria.
OFAC discriminates, based on country of birth, residency, and citizenship, against some of the most vulnerable people around the world. For years, particularly people of middle eastern descent have been subject to no-notice account freezes and account closures, if they are even able to open a bank account at all - all thanks to OFAC.
OFAC, first and foremost, targets the little people. Those in big business, from oil traders to weapons manufacturers to heads of state, have little issues transacting their money through the traditional financial system even with OFAC sanctions in place - while the big banks facilitating those transactions will get no more than a slap on the wrist.
OFACs strategy is simple: cut off entire populations from the global financial system, and with this from accessing basic needs, and hope for a revolte within the country OFAC is targeting. The US has long been the world‘s biggest bully, and OFAC is its favorite enforcement arm. Now, amboss is attempting to turn *you* into accomplices for profit.
From a human rights perspective, this should simply be unacceptable. Bitcoin has been a lifeline for many subject to OFACs racist, discriminatory policies. Especially for smaller payments, such as remittances, LN is vital, and often the only way for individuals to support their families in oppressive regimes; not to mention the use of btc for NGOs cut off from fundraising.
Most importantly, even when running a routing node, you have no obligations to comply with OFAC at all, as your service to the network is non-custodial (although this changes when you begin charging routing fees).
Amboss yet seems determined to unbank the Bitcoin banked for their own financial gain, and is selling it to you, LN users, as a convenience product to advert „the death of bitcoin through compliance“ - because if only you adhere to OFACs policies marginalizing the few will you decrease your own risk of getting debanked. Freedom for me, not freedom for thee.
Amboss‘ OFAC moneygrab should be unacceptable for anyone that *actually* cares about freedom - freedom for those who think, speak, look, live differently; for those we may not agree with or understand; for those who may one day have to protect *our* freedoms, just as it is our responsibility to protect their freedoms today.
But the Lightning Network is still young, and we should not let ourselves be bullied into racist and for most node runners quite frankly completely unnecessary policies by greedy assholes trying to make a big buck off of others misfortunes. Lets do what‘s always worked: boycott.
If you believe for bitcoin to be freedom money, and want it to remain an important tool for human rights, close all channels to amboss nodes and stop using their services immediately. Speak out against their company and products. Tell your friends to close channels to amboss, tell your friends to tell their friends, you know how this works.
Mentioning the need for more privacy and surveillance resistance in bitcoin, while simultaneously building the premier surveillance service for the Lightning Network in existence today, really is a mouthful.
Freedom of transaction is a human right, not a marketing phrase to sell your shitty products on in a powerpoint. I have always boycotted Amboss, and I hope now that the company is showing its true colors more will do the same.
Silen Zara retweeted
Looks like someone managed to get a backdoor into ssh in Fedora and Debian testing. Patch systems ASAP. openwall.com/lists/oss-secur…
Any (potential) peer interested in earning via KeySend? You would earn a percentage of the inbound you bring.
Something like if I charge you 200ppm, you get a % of that 200ppm when you route towards me.
Not working on it yet but might if there is interest.
A fun project for LN would be a KeySend incentive system for routing nodes to reward traffic that goes to desired peers with low outflow. It would be pretty simple, setup your peers where you want more outflow and then whichever inbound peer delivers this traffic, send them a %.
1
1
196
I've always wondered how River is able to maintain healthy inbound while facilitating LOOP outs.
Now I know.
My advice: think carefully before opening a channel to them.
1
2
1,317
Silen Zara retweeted
As promised, a deep-dive on Taproot Channel Transactions 🥕⚡️ You might need a few shots of espresso for this one! ellemouton.com/posts/taproot…
#Bitcoin #LightningNetwork













