OSGuild simplifies the path into Bitcoin open source for new developers. Contributors practice on forked real world projects, earn points for their work, and receive feedback from maintainers.
TEAM · 3
MEMBER SINCE 2026
§01 · EVENT BADGES
1 edition attended.
§02 · HACKATHON PROJECTS
Built at the hackathon.
Sadiq Rabiu
Shehu
§03 · TALKS & PANELS
On stage.
Gating APIs with Lightning: A Hands-On L402 Workshop Using Aperture
L402 is an open standard that turns Lightning into an authentication and payment layer for APIs. Instead of API keys and subscription plans, your service issues a Lightning invoice — the client pays, gets a macaroon, and gains access. It's permissionless, programmable, and built on open-source tooling. In this hands-on workshop, we'll build an L402-gated API from scratch using Aperture, the open-source reverse proxy from the LND ecosystem. Participants will work in a pre-configured regtest environment (Docker-based, no mainnet sats needed) and walk through the full cycle: setting up a backend service, placing it behind Aperture, configuring macaroon-based access, and testing the 402 Payment Required flow from the client side.
Onion Messages: How Lightning Learned to Talk Beyond Payments
Lightning Network is best known for routing payments, but a quieter revolution has been happening in the open: onion messages. Built on the same onion routing primitives that move sats, onion messages give Lightning a general-purpose, privacy-preserving communication layer — no payment required. This talk walks through the journey from problem to protocol. We'll start with how onion routing works for payments, then explore why the network needed a messaging layer beyond HTLCs — and how the open spec process produced one. We'll cover the core mechanism (how onion messages reuse Sphinx routing for arbitrary data), what they unlock (BOLT12 offers, blinded paths, async payments), and the privacy tradeoffs involved.