BitMEX renewed Rene Pickhardt’s grant, extending it for 6 additional months. Rene’s work has been quite influential on how we envision liquidity on the Lightning Network, from a novel routing algorithm (Pickhardt Payment) to better models for liquidity management (why would the optimal state for all channels be a 50/50 repartition of funds?) and their consequences (for example, flow control).
That was quick! The Adopting Bitcoin team already published lots of replays (all of them?) from the conference. I don’t know about you, but I know what I’ll be doing of my free time this week. Replays are divided in 4 playlists, one for each stage and day: Bitfinex Stage Day 1, Day 2, Galoy Stage Day 1, Day 2.
The latest LightningReport by LNCapital further cements the observation that big nodes (eg. from exchanges, wallets, services and large businesses) are eating the network in terms of capacity. However, half of the network capacity is still contributed by routing nodes, while the rest of the nodes contribution to the overall capacity is down to around 10%.
Blockstream lauched Build on L2 (BOL2), a community for engineers, designers and contributors who are working (or want to work) on Lightning. The aim of the initiative is to foster collaborations in all forms, from joined projects to hackathons to physical events and more!
On the same week, node management tool BoltObserver and studio PeakShift released the Lightning Landscape, a searchable data platform for the Lightning ecosystem with more than 1400 projects and companies listed so far. Entries can be filtered by categories and tags, allowing you to quickly find the project you’re looking for even if you don’t know its name. I’d love to have features such as community tagging, or signaling features for projects allowing them to display that they’re looking for talents or investors, for example. But the brand new platform is already, as it is, impressively complete and enjoyable to use.
The ScarceCity team launched a new marketplace called SatsCrap where people can sell and buy stuff directly with Bitcoin. A good way to stack more sats directly, or to get your hands on some great deals. There’s no signup required, and SatsCrap pays itself with a 10% commission on sells. Regarding customer protection, sellers are required to pay a listing deposit equalling 10% of the item’s price, which will be refunded if everything goes well. On the other side, buyers are required to video record the item’s unboxing.
Wallet of Satoshi <> BTC Map
WoS has also become a sponsor of the open source project.
Wallets & Tools
Routing Node Extracted Value (RNEV)
Lightning currently uses HTLCs to trustlessly route payments accross the network. HTLCs are conditional payments, which the receiver can unlock to get the funds by revealing a secret, commonly called the preimage. When a payment goes through multiples nodes to reach its final destination, what happens behind the scenes is that every node sends an HTLC to the next. All of this HTLCs use the same secret preimage and are then resolved en cascade starting from the final node.
The reason all this HTLCs use the same preimage is because the hash of said preimage was placed in the payment’s invoice by the receiver. There is hence one preimage per payment/invoice and, once a payment is settled, every node involved in this payment has learnt the corresponding preimage. It means that if someone later tries to fulfill the same payment (for example, using an invoice posted on Twitter), any node that was part of the previous payment as well doesn’t need to forward the HTLC to the next, as they already know the preimage, and can instead claim the payment for themselves as if they were the final recipient.
The preimage-stealer tool does just that: when a new HTLC enters your node, it checks whether it already knows the corresponding preimage or not. If not, it forwards the HTLC as usual. Else, it stops forwarding and either steal the funds or just increment a counter of how many funds it could have stolen (that’s the watch-only mode).
Preimage stealing isn’t a new idea, and I’m honestly quite surpised there wasn’t a tool to do that before. This kind of attack will be addresses when we switch from HTLCs to PTLCs, but in the meantime can be mitigated by avoiding to pay publicly posted invoices (which shouldn’t exist in the first place, as it carries a privacy risk for the receiver).
BoltObserver released the beta of a new tool called LiquidOps that helps you get valuable and actionnable insights for your node. The tool connects to your node either via read-only macaroons or an open source agent, and then sends data to BoltObserver, allowing you to display channel data in dashboards and, more importantly, automatically receive custom alerts when certain thresolds are hit (balance depleted on a given channel, new channel, unavailable node, etc.).
New Alby Release
Alby published their latest release, which notably brings Core Lightning support to the browser extension, thanks to the commando plugin. Alby now supports all major immplementations, and this new Core Lightning integration already shows its power with the ability to open dual-funded channels in the browser. Impressive!
La foudre en frappant éveille une étincelle
Qui s’élève, aspirée, virevolte et explose
En un millier de petits, petits fragments d’étoile
Qui retombent sur la terre avec les giboulées.
If you enjoyed this recap, you can show your appreciation by throwing a few coins to fanis @ lnmarkets.com, by scanning or clicking the QR code.