Skip to main content
 

Lightning Network Resources

2 min read

I hosted a small session on the Bitcoin Lightning Network at Hacker Beach last night, and promised to share all the resources from it somewhere. Hence, here's a random list of things you can read to learn about Lightning Network, and also start using/testing it.

Understanding the protocol

* The original Lightning Network paper
* Slides from a Lightning Network talk at the SF Bitcoin Devs meetup (Feb 2015) -- Slightly outdated, but contains a lot of the basics (from the authors of the paper)
The Lightning RFCs / BOLTs -- This repo contains the various protocol specifications. Also, scroll down in the README for a nice short introduction section.
* Lightning network in depth, part 1: Payment channels
* Lightning network in depth, part 2: HTLC and payment routing
lightning-onion -- Repo containing the code for LND's onion routing. Also, check the README for a broad overview of what this means for the Lightning Network.

Software

LND Developer Site -- Resources and documentation for the Lightning Network Daemon (LND)
c-lightning -- A Lightning Network implementation in C
Spark Wallet -- A GUI client for c-lighnting
eclair --
A scala implementation of the Lightning Network
eclair-mobile --
An Android wallet for the Lightning Network
Lightning Wallet for Android -- A fork of eclair with support for receiving payments (includes watchtowers)

 Stats and visualizations

1ml.com -- Lightning Network Search and Analysis Engine
* Bitcoin Visuals: Lightning Network statistics

 
 
 

Was wondering about how exactly maps.me submits user edits back to OpenStreetMap, and I just randomly stumbled across one of the ways they do it: https://storage.5apps.com/basti/public/shares/190109-0552-Screenshot%20from%202019-01-09%2013-47-46....

 
 
 

Recently stumbled across umap, which is an alternative to Google Maps for creating and sharing your own maps with POIs and such. Works really well so far, and the feature set is fantastic! http://umap.openstreetmap.fr

 
 
 
 
 
 

Adding a German word list for standardized Bitcoin HD passphrases is more difficult than you'd think: https://github.com/bitcoin/bips/pull/721

 

"I very recently worked on the Edge team, and one of the reasons we decided to end EdgeHTML was because Google kept making changes to its sites that broke other browsers, and we couldn't keep up." https://news.ycombinator.com/item?id=18697824

 

Who controls Bitcoin Core? TL;DR: nobody. https://medium.com/@lopp/who-controls-bitcoin-core-c55c0af91b8a

 
 

Cloudflare's work on IPFS, Tor, crypto libraries, and some fun facts

3 min read

I just finished listening to a rather interesting podcast episode with Cloudflare's "Chief Cryptographer" Nick Sullivan and wanted to recommend it to people who are interested in any of the mentioned topics.

Especially so, because Cloudflare is arguably one of the most controversial companies involved in running the Internet, as they're not just serving a considerable amount of Web traffic via their CDN, but also a considerable amount of DNS traffic via their public 1.1.1.1 service. Both come with a lot of responsibility, even more so in combination, due to a large amout of trust being centralized in a single corporate entity.

The topics discussed in the episode (citing from the podcast's summary):

  • Nick’s background as a cryptographer and previous position at Apple
  • The Internet’s infrastructure and trust model
  • How Cloudflare is experimenting with IPFS
  • The challenges to hosting static websites with IPFS
  • Cloudflare’s Onion routing service (Tor) and the benefits to users
  • The Roughtime protocol and encrypted SNI
  • Cloudflare’s contribution to open-source cryptography libraries
  • The vulnerabilities of DNS and Cloudflare’s free private DNS service (1.1.1.1)

Interesting tidbits

On IPFS

Probably the most exciting news, which I somehow missed or forgot about, is that Cloudflare have launched a public IPFS HTTP gateway called Distributed Web Gateway during their Crypto Week a few months ago.

This is great, because not only are Cloudflare nodes around the world now relaying IPFS data to other IPFS nodes, in addition to serving cached content via their gateway. But also because IPFS is a content-addressable storage system. Which means, a client can actually verify themselves, that the content which was delivered by the CDN is exactly what was promised, based on the hash/URL of the resource requested.

This eliminates one of the main trust issues with CDN delivery: ensuring content integrity from source to end user. And in this case, the source is not even a server, but a completely decentralized peer-to-peer network. Win-win-win in my book.

On Tor

According to Nick, most incoming traffic to CDNs from Tor is actually attack traffic, due to the fact that it's impossible to trace back (unless you're the NSA for all we know). So for the longest time you actually had to fill in CAPTCHA's for Cloudflare-cached sites when browsing via Tor.

However, also during Crypto Week, Cloudflare introduced an onion routing service, which in combination with some smart HTTP/2 usage, and implemented in coordination with the Tor developers, solves the problem for anyone using Tor Browser 8.0+. As Cloudflare are actually hosting all of their CDN content directly in the Tor network with this change (enabled by default for all customers), Tor users now don't even have to go through Tor exit nodes in order to retrieve that content.

On decentralized DNS in 1.1.1.1

When asked about Namecoin, Nick's answer was rather surprising to me:

We've talked to the Namecoin folks, we've talked to the folks at Ethereum [...] Right now we're mostly investing in how we can make the IPFS gateway better. [...] But down the line, you shouldn't be surprised to see any one of those pop up.

On the 1.1.1.1 IP address

Cloudflare didn't actually buy the 1.1.1.1 address (or rather the space it's in). APNIC is lending it to them for free, because nobody else wants to have that much dummy traffic coming to their network. ¯\_(ツ)_/¯

 
 

This blog post for remote-work newbies also contains some useful tips for more experienced remoties: https://24ways.org/2018/thriving-as-a-remote-worker/

 

A personal update on Hacker Beach #7

2 min read

After finally having booked my incoming flight for Hacker Beach #7, which is going to take place on the Phillippines in January, I'm getting genuinely excited about it.

Aside from every single one of the past 6 editions having been amazing in their own way, I'm mostly looking forward to clearing my schedule of for-profit work, and yet again spending most of January on developing and contributing to free and open-source software.

The things I'll be hacking on will include many pieces of software from both the remoteStorage ecosystem as well as the wider Kosmos project. But I'm also planning to spend some time on improving my IndieWeb setup, and experimenting more with Lightning Network.

I'm also looking forward, as always, to doing these things together with old and new friends, and exchanging knowledge and experience, while escaping the cold Northern winter together. Just for one example, I think I would've never switched to Linux a few years ago, and learned so much about it since then, without the privilege of having had bkero explain to me a thousand things in the past.

So, in the spirit of p2p learning, I'm hereby offering free mentorship for anyone wanting to get involved with contributing to the projects (or wider areas of software) that I mentioned above!

For outdoor activities, while others might be more excited about the excellent diving around Coron, personally, I'm more keen on the mountain-biking. In fact, I'm planning to bring a bike this year, including bike packing bags, so I'll be able to explore not just Busuanga island, but potentially more of the Phillippines, on two wheels before and/or after Hacker Beach.

---

If you're interested in joining us this coming January, and you haven't had the pleasure to catch a Hacker Beach in the past: you can get in touch with people in on Freenode IRC, and you can also follow and talk to us on the fediverse (Mastodon, GNUSocial, Pleroma, etc.), and if need be on Twitter.

An IndieWeb Webring 🕸💍