Power your Lightning node with OpenBSD to reduce its attack surface
The Lightning Network has grown tremendously since it reached the Bitcoin mainnet back in early 2018. The network is slowly reaching maturity with all implementations now in beta and new features being added steadily — like multi-path payments, keysend, large Wumbo channels, and new privacy improvements.
Exciting new features like Wumbo channels and Multi-Part Payments (MPP) coming to the Lightning Network also means we have a bigger need to fortify the systems our nodes are running on. Large amounts of BTC in a hot wallet is a sure bet…
Stay humble. Stack stats.
Unlike Bitcoin nodes, which must process all payments on the network, Lightning nodes only process the payments routed through them. Therefore the bottleneck to payment throughput becomes a matter of connection latency, hardware performance, and channel liquidity (depending on the payment size).
Blockstream’s c-lightning implementation is suitable for running on a wide range of hardware. Designed to be lightweight and performant, c-lightning is also extendable with plugins. Plugins allow you to customize your c-lightning node with additional features to fit your needs. This means you can run a lightweight bare bones c-lightning instance on the lowest…
Blockstream Satellite is a service which provides a broadcast of Bitcoin blockchain data, Lightning Network gossip data, and users’ custom data via a network of geosynchronous satellites. The one-way transmission provides a degree of privacy that is unique in the communications industry and is free to use for anyone who has the hardware able to receive the transmission.
While people can use the service to send arbitrary small pieces of data like text messages or pictures, it also creates an opportunity to mass-broadcast bigger, more important chunks of data to a global-scale coverage area.
tl;dr: Liquid makes it exceptionally easy to issue new assets. Scroll down to skip the tech details to learn how to start issuing assets.
Legacy platforms today rely on smart contract developers handwriting or customizing already written code in order to issue tokens or assets. This has unfortunately resulted in some bugs being uncovered that could allow theft — with one in particular so it nasty it could be used to drain exchanges into insolvency. This sort of bolted-on approach has some apparent flaws since it allows unintentional token contract inconsistencies and incompatibilities.
I’ve been inspired to write a post about something that occurred recently on Bitcoin Twitter that is important to document. What happened was a clash of Bitcoin values and thing-that-isn’t-Bitcoin values. This is important to document because it shows a few things.
But before I can explain why it was important I have to tell you what happened.
Without diving into all of the people involved and all of the individual tweets, I can sum the exchanges up into the following:
How does anyone censor something abstract and intangible; something that can consist of an arrangement of numbers and letters, and can be transported via any medium? What do you do? Ban pen and paper? Phone calls and the spoken word? Smoke signals? Morse code? To what end?
What about the electronic transmission of this data that can be hidden in other data, like images or music? You’re going to ban music and puppy pictures?
Being able to effectively censor Bitcoin means monitoring and potentially jamming all means of communication in every nation and jurisdiction. A task so insurmountable, and so…
This guide is for building and using
c-lightning on the Liquid sidechain to create Lightning payment channels. With these payment channels, users can transact Liquid-BTC (bitcoin transferred to the Liquid sidechain) instantly and privately.
Support for Confidential Transactions and Issued Assets is planned, so users will be able to transact any asset issued on the Liquid Network in a Lightning payment channel — such as tokenized fiat, crypto assets, attested assets (e.g. gold coins), or completely new assets. Also, support for swapping on-chain BTC for L-BTC in a payment channel is being worked on.
c-lightning on Liquid is practically…
tl;dr: A guide to use WiFi to connect your local area with Bitcoin and arbitrary data received with Blockstream Satellite.
Build a Blockstream Satellite Receiver
* Install Ubuntu 18.04
* Install Blockstream Satellite software
* Align the dish to the satelliteConnect WiFi Hardware to Satellite Receiver
* Configure Connection Sharing
* Hand out IP address to clientsPart 2: goTenna Mesh Integration
* Coming Soon
Blockstream Satellite beams down Bitcoin data to nearly all of the populated areas of Earth. Anyone can receive the data for free, and it’s possible to run a Bitcoin node strictly off of the…
c-lightning node previously has required a “clear” net address (ipv4 / ipv6) to connect to other nodes. This has certain privacy implications. As a result, one may would prefer to rent a VPS to run their node on in order to not expose their home IP address.
c-lightning has support for Tor, so a user can run their node behind Tor and even generate a
.onion address for others to connect to to open channels — all at home and without exposing the user’s home IP address.
To run your
c-lightning node over Tor, it takes four fairly…
With the advent of Blockstream Satellite and widely broadcasted, passively-receivable Bitcoin data, a new era of Bitcoin adoption can occur. Areas without access to fast broadband connections can now trustlessly verify Bitcoin blocks and transactions, and receive BTC discreetly with common cheap hardware. With the Satellite API, those same areas can now receive arbitrary data — current market data, private messages, and data from exciting new use cases not thought of yet. All free. The broadcasts are free and the software is free with code available for auditing and improvement by the community.
For the first time, most of the…