Lightning (And Email) Addresses In Vida
Lightning Addresses are now a thing in Vida, and every user gets one (it’s basically <your-username>@vida.page, so for example mine is email@example.com). But where it gets really interesting is that each Lightning Address is also a paywalled email address. To reach you via email, someone would therefore have to pay the same amount as the one for a one minute call.
I really like the idea of merging Lightning and Email addresses (although it won’t make dealing with mailto: and lightning: prefixes easier). The only thing that is a bit frustrating here is that the sender is required to setup a Vida account in order to pay and get the mail to your inbox, rather than being able to simply scan a QR Code or copy-paste an invoice.
By the way, this feels like a good opportunity to let you know I have a Vida page myself. I’ll always answer Twitter DMs anyway, but if you which to reach me more quickly or just support my work, this might be a good way (wink wink).
BoltFun Finalists Announced
BoltFun announced the finalists of the Legends of Lightning tournaments, with 2 categories (Building for Africa and Global Adoption) and 8 projects selected for each. Among the finalists are some projects that we already met in Latest Strikes, such as BTC Map, Lightsats, Mutiny Web or nolooking. We also met AgriMint from the “Building for Africa” track when it won the Designathon back in October.
I’ll let you check out all the finalists by yourself, but I must confess I remain amazed by how much talent and creativity bitcoiners have. From Afromnemonics (BIP39 wordlist in Swahili – 200 million speakers worldwide!) to Sats2Data (it’s in the name: turn sats into mobile data and airtime), all the projecs are really inspiring!
Don’t forget to tune in tomorrow for the finals, starting at 14:45 UTC.
SlashTag Authentication In Some Places
Slashtags are a new kind of “identity” that allow you to create passwordless accounts, send and receive money from and to “contacts”, subscribe to personnalized data feeds, and so on. They are currently only supported by the BitKit wallet, and authenticating via Slashtag is now supported on Starbackr and LN Markets, alongside LNURL-Auth.
You Can Now Charge Your EV With Sats In Europe
Satimoto launched in Europe, with more than 20,000 locations covered in many countries. If you manage to get on the early access (or to wait a bit), Satimoto will allow you to charge your electric vehicle with sats, without any registration, KYC nor custody of funds. Some bitcoiners are already tring it in the wild. ⚡
StackerNews: Sats Now Affect Ranking
You may have thought (like me) that it was already the case, but sats now affect ranking on StackerNews. The release post gets into more details as to how exactly sats impact ranking, but the key things to remember are other parameters (such as trust) still influence ranking, and that the effect of sats is logarithmic (ten times more sats only raises the ranking score by 1). Also, StackerNews will now take 10% of every tip in order to prevent sybil attacks, where someone could propel themselves to the top for free by simply tipping themselves with a secondary account.
I’m not yet sure sats tipped are the best way to measure the quality of content, but it’s definitely worth giving a try!
Wallets & Tools
Anonsats is a “Chaumian ecash payment and settlement system” that leverages Bitcoin, Lightning, LNBits and Cashu to enable users to send and receive money with increased privacy, with the notable drawback of giving up the self-custody of their funds.
Users can create a new wallet on a custodial instance (a la LNBits) and send sats to this new wallet, for example using the included Lightning Address. They can then send the funds anywhere, or convert them to Cashu tokens. Cashu tokens can then be sent natively between users of the same mint (eg, server), or even sent to a different mint, through Lightning.
A cool feature, derived from the custodiality of this setup, is that users can access their wallet from anywhere as long as they have an internet connection (for example, from a demo machine in an Apple store). On the privacy front, users profit from the strong privacy guarantees of Cashu and Chaumian e-cash. But all that requires trusting the central server.
You can give it a try here, but keep in mind it’s still alpha software, so only send tiny amounts you’re prepared to lose.
Specs & Implems
New Minor LND Release
LND vO.15.5-beta is here, with a bunch of bug fixes. Notably:
- a bug in Taproot key tweaking that affected remote signing setups,
- an unnecessary CPU activity when waiting for a peer’s
funding_lockedmessage, before announcing the channel to the rest of the network (fix consists in waiting 1 second between each check of whether we received the peer’s message or not),
- the wallet birthday wasn’t correctly taken into account when creating a watch-only wallet, prompting the wallet to rescan the whole chain instead of just the useful portion from the wallet’s birthday to now.
Core Lightning v.22.11
With this new release, Core Lightning changes its versioning scheme for a date-based one (22.11 stands for November 2022) but keeps its very funny naming policy. Core Lightning v22.11, named “Alameda Yield Generator”, comes with a number of new features, bug fixes and enhancements.
This blog post goes into some details for a few of them, and is very pleasant to read. To put it in a nutshell:
- a new standalone pluging manager called “reckless” comes into town, allowing node operators to install and start new plugins with one command (no more git cloning and config editing),
- the autoclean tool has become more powerful, helping operators keep their node strong and fast.
You can scroll through the full release notes to see all the changes. You’ll see for example that, following its eradication from the BOLTs, the legacy onion format is also bowing out from Core Lightning.
A new release of Eclair has landed! Version 0.8.0 includes three new features, a breaking change, and lots of improvements and bug fixes:
- make “private” (I mean, unannounced) channels even more private. With channels aliases, you can give channels arbitrary identifiers, as long as your peer supports them as well. This way, you don’t have to leak the underlying UTXOs of your unannounced channels in routing hints anymore. Great for privacy!
- in the midst of the Full-RBF debate, zero-conf channels make their apparition in Eclair. They allow users to consider a channel as usable as soon as the funding transaction is published, without having to wait for confirmations. Because of the trust implications of zero-conf channels, they are disabled by default and can only be enabled on a peer-by-peer basis, allowing you to activate them only with peers you trust (enough),
- experimental support for dual-funding: if your peer supports it and you enabled this opt-in feature, your channel open will automatically use dual-funding, where both peers can contribute funds to the channel funding and the funding transaction can be fee bumped with RBF. However, note that in this first version, the “dual” aspect only concerns fee-bumping, as it is not yet possible for the non-initiator to contribute funds to the channel (soon™),
- Eclair v0.8.0 requires Bitcoin Core v23 or higher, dropping support for earlier versions (that’s the breaking change). Note that you may need to change your Bitcoin Core configuration if not done already, so that Core only generates SegWit addresses, notably for change.
Research & Papers
A New Website For Lightning Privacy
Tony Giorgio, futurepaul, Ben Carman, Evan Kaloudis and Max Hillebrand published a new resource on Lightning privacy, covering on-chain privacy “contagion”, routing analysis and what Blinded Paths and Trampoline Routing bring to the table.
DLCs On Lightning (On Mainnet)
A DLC is a channel between two peers (kind of like a Lightning channels) where the repartition of funds in the end depends on a specific result, provided by a well-determined oracle. With DLCs, one can take part in sophisticated “contracts” (betting, trading, etc.) without giving up the custody of their coins.
However, DLCs on-chain don’t scale very well, as each new contract (for example, betting on the price of Bitcoin tomorrow) requires setting a new DLC (one on-chain transaction) and resolving it at due date (another on-chain transaction). By putting them inside Lightning channels, one can create and settle HTLCs off-chain, and even renew contracts without closing them (very useful for applications such as perpetual CFDs).
Of course, doing so requires some decent engineering, to properly split the funds inside the channel between those involved in the DLC and those that remain available for routing1, ensure contracts can be safely and trustlessly renewed, and everything can be brought back on-chain if needed.
With this building block, the possibilities offered by channels on top of Bitcoin start to become quite mesmerizing. Remember the Synthetic Dollar in Bitcoin Beach, Kollider or LN Markets? You could very well set them up directy in your own Lightning channel by creating a DLC with your peer where you short Bitcoin’s price, allowing your channel’s balance to stay approximately the same in dollars term, in spite of Bitcoin’s volatility, which could be quite useful for day-to-day spending.
However, as the Crypto Garage team emphasizes, it is not yet possible to route DLC’s accross the Lightning Network, so it’s too early to speak about Bitcoin-native “stablecoins”. No big deal: stablechannels is cool too, isn’t it?
Que de ténèbres alentours!
L’hiver est venu dans un bruissement.
Il fait noir avant que n’entrent en gare
Les trains partis tôt mais venant de loin
Qui, de nuit en nuit,
S’en vont toujours vers de nouveaux départs.
Want to receive Latest Strikes straight to your inbox every week? Couldn’t be easier: subscribe to LN Markets Ghost blog and you’re all set (remember to confirm your subscription by clicking the link sent via email).
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.
Else, we would need to update the (potentially numerous) DLC’s Contract Execution Transactions every time a Lightning transaction is routed in the node. ↩︎