<p>Streaming payments is not part of the lightning network protocol yet.</p>

<p>However you can build a lightning app that simulates exactly this. There was a demo by alekos Filini on lädt years lightning residency. Check out <a href="https://youtu.be/IlSVTir_9Ns" rel="nofollow noreferrer">https://youtu.be/IlSVTir_9Ns</a></p>

<p>When AMP is coming streaming payments could be stimulated with AMP by setting up more and more routes. But that would be rather fancy. </p>

<p>So I guess you create an app on top of lightning to solve streaming payments</p>

CC BY-SA 4.0
2019-06-02T15:43:06.557Z
*However you can build a lightning app that simulates exactly this.* - I'm stealing this idea. Not exactly stealing because I feel partially responsible of thinking about it, just not being fully aware if this is already a part of the protocol... Also related: https://github.com/lightningnetwork/lightning-rfc/issues/399 *(seems like the receiving node needs to create the invoice first in order to receive a payment)*
Mars Robertson
CC BY-SA 4.0
2019-06-02T13:28:07.167Z
2019-06-02T13:28:07.167Z
Rene Pickhardt
<p>Examples:</p>

<ul>
<li>Car insurance: $1000 per year.</li>
<li>Legal consultation: $500 per hour.</li>
<li>Visiting a website: $100 per hour.</li>
</ul>

<p>Assuming <code>1 BTC = $8000</code></p>

<p><code>1 hour = $100 = 0.0125 BTC = 1,250,000 sat</code></p>

<p><code>1 second = 1,250,000 sat / 3600 = 347.22 sat</code></p>

<p>I could generate a new invoice and pay it every second. </p>

<h3>Continous stream of value?</h3>

<p>I was thinking about something else:</p>

<blockquote>
  <p>until further notice, please charge me 3472.22 sat per second</p>
</blockquote>

<p>To avoid me going offline, there could 10 second heartbeat.</p>

<h3>Is it overcomplicated?</h3>

<p>Because of speed of light limit and network propagation, <code>1s</code> resolution is good enough, no need for a continous stream of value.</p>

<p>Issuing a new invoice every second is a simple workaround and no need to overcomplicate.</p>

<p><strong>Or maybe it exists natively?</strong></p>

<p><strong>EDIT / UPDATE:</strong> <a href="https://github.com/lightningnetwork/lightning-rfc/wiki/Brainstorming#streaming-payments" rel="nofollow noreferrer">https://github.com/lightningnetwork/lightning-rfc/wiki/Brainstorming#streaming-payments</a></p>

<lightning-network><micropaymentchannels><channels>
Does Lightning Network has concept of continuous stream of value?
Mars Robertson
# Does Lightning Network has concept of continuous stream of value?

(Asked by: username_0 on 2019-06-02)

Examples:

* Car insurance: $1000 per year.
* Legal consultation: $500 per hour.
* Visiting a website: $100 per hour.

Assuming `1 BTC = $8000`

`1 hour = $100 = 0.0125 BTC = 1,250,000 sat`

`1 second = 1,250,000 sat / 3600 = 347.22 sat`

I could generate a new invoice and pay it every second.

### Continous stream of value?

I was thinking about something else:

> until further notice, please charge me 3472.22 sat per second

To avoid me going offline, there could 10 second heartbeat.

### Is it overcomplicated?

Because of speed of light limit and network propagation, `1s` resolution is good enough, no need for a continous stream of value.

Issuing a new invoice every second is a simple workaround and no need to overcomplicate.

**Or maybe it exists natively?**

**EDIT / UPDATE:** <https://github.com/lightningnetwork/lightning-rfc/wiki/Brainstorming#streaming-payments>

**Tags:** lightning-network, micropaymentchannels, channels


---

## 1 answers

### Answer by username_1 on 2019-06-02. Score: 2

Streaming payments is not part of the lightning network protocol yet.

However you can build a lightning app that simulates exactly this. There was a demo by alekos Filini on lädt years lightning residency. Check out <https://youtu.be/IlSVTir_9Ns>

When AMP is coming streaming payments could be stimulated with AMP by setting up more and more routes. But that would be rather fancy.

So I guess you create an app on top of lightning to solve streaming payments

> **Comments:**
> **username_0**: *However you can build a lightning app that simulates exactly this.* - I'm stealing this idea. Not exactly stealing because I feel partially responsible of thinking about it, just not being fully aware if this is already a part of the protocol... Also related: https://github.com/lightningnetwork/lightning-rfc/issues/399 *(seems like the receiving node needs to create the invoice first in order to receive a payment)*  

---

