W3C home > Mailing lists > Public > public-webpayments@w3.org > January 2019

Re: instant web payments via the lightning network

From: Melvin Carvalho <melvincarvalho@gmail.com>
Date: Mon, 14 Jan 2019 12:50:00 +0100
Message-ID: <CAKaEYhJ-tad-yMK-KSJaAaqiALismPbz2-r8PdwDjKHN4Bv2FA@mail.gmail.com>
To: Michael Bumann <hello@michaelbumann.com>
Cc: Web Payments <public-webpayments@w3.org>
On Mon, 14 Jan 2019 at 11:30, Michael Bumann <hello@michaelbumann.com>

> Hi Melvin,
> yeah, I've been experimenting with the Bitcoin lightning network for a
> while and I am pretty excited about the state and how easy it is to build
> on top of it.

Hi, Great!

Funnily enough I was just reading your page, and realized it was you :

Tim did actually a while back ask me to interact with this group regarding
http 402.  Some work has been done on that, including by me, and it would
be great to compare notes at some point.  Or maybe flesh out use cases.

> Did you see/use lightning browser extension "joule"[1]?  It brings
> lightning payments to the browser - and there has been some discussion
> around supporting web payment standards - maybe somebody familiar can help?

I have it installed, but dont fully understand the fine details.  When my
casa node arrives I'll be able to try it out with my own node.  But I might
set up a raspblitz while I wait.

I was lead to your blog post from :


> I am wondering how to make it easier for content providers to integrate LN
> payments and also experimented with lightning payments for API requests [2].

I have written in the past working code for pay walls, with a dance around
http 402, and in fact that's my current use case.

Do you think some areas of this work flow would benefit from

With solid it's possible to access control content, and give back a 4xx.
We dont yet return 402s but I've custom hacked a server to do that.  I'm
not quite sure how a server will be able to know to send a 402.

> [1] https://lightningjoule.com/
> [2]
> http://michaelbumann.com/post/180389589277/bitcoin-lightning-machine-to-machine-api-payments
> [2] https://github.com/bumi/ln-markdown-to-pdf
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Saturday, January 12, 2019 6:04 PM, Melvin Carvalho <
> melvincarvalho@gmail.com> wrote:
> > I am curious if any of this group is interested in the lightning network
> [1].
> >
> > For those that are unaware, it is a system built on top of block chains
> that allow zero cost instant payments in a zero trust environment.
> >
> > There has been lots of innovation already this year, and it seems to be
> growing fast.  One service that impressed me is a custodial service built
> on top of twitter that allows you to add a tip jar based on your twitter
> account.
> >
> > https://tippin.me/
> >
> > This is a really easy way for non technical people to experience web
> payments and bitcoin in the browser, without the overhead of a high
> technical barrier to entry, or downloading a wallet.
> >
> > Additionally I have added this to my sollid profile using the the foaf :
> tipjar predicate that has been around for about a decade but never really
> used.  The I have added it looks as follows :
> >
> > In turtle :
> >
> > </#me> <http://xmlns.com/foaf/0.1/tipjar> <
> https://tippin.me/@melvincarvalho> .
> >
> > In RDFa :
> >
> > <a target="_blank" rel="http://xmlns.com/foaf/0.1/tipjar" href="
> https://tippin.me/@melvincarvalho">https://tippin.me/@melvincarvalho</a>
> >
> > There are also new solutions such as a mobile wallet that receives
> payments (blue wallet), decentralized apps (Lapps) and ability to run your
> own node eg on a raspberry pi.
> >
> > If anyone is playing around in this space would love to hear from you,
> or if you'd like to get started and have, say a tippin me account, I'd be
> happy to send some satoshis (the unit of currency) to play around with.
> >
> > I think this brings forth an exciting new era of instant payments in the
> browser.  Would love to hear from anyone else that is interested in this
> tech.
> >
> > [1] http://lightning.network
Received on Monday, 14 January 2019 11:50:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:07:52 UTC