PPPs: Week 1 - [email protected]

This week I worked some initial integration of lnproxy with the lnurl protcol. I had no experience working with lnurl before this and I'm incredibly impressed with how easy it was write my own LUD-06: payRequest server and how easy it was to then turn that into a lightning address bridge. The ecosystem is great and I want to brainstorm some other ways I could add lnproxy to the mix.

Progress ✅

• Initial support for custom routing budgets in the lnproxy api: github.com/lnproxy/lnproxy/commit/a4295c4a5539244c10acdfb4bb822d6bed7844b9
  This is necessary to fit neatly into the lnurl payment request spec since wallets make sure that invoice amounts match.

• Minimalist lightning address bridge server that automatically wraps all invoices with configurable lnproxy node and checks to make sure that funds are never at risk: github.com/lnproxy/lnproxy-address
  Try donating to [email protected]

• Pull request to github.com/nbd-wtf/satdress adding support for optionally wrapping invoices with lnproxy: github.com/nbd-wtf/satdress/pull/42
  This is important because it includes a web gui to allow other users to add credentials for their own nodes so that a single domain can be used for many users.

Plans 📆

• Improve the lightning address bridge server code and release binaries

• Get the PR to satdress merged

• Start offering [email protected] addresses

Problems ✋

• Figure out issues providing a bridge server over tor

• Figure out a good way to keep the namespace sane like sendsats.lol