pull down to refresh

0 sats \ 4 replies \ @jeff 10 Apr 2022 \ parent \ on: Impervious.ai Announcement - Bitcoin 2022 Conference bitcoin
It doesn't smell like they are doing that back-and-forth concept over lightning itself for the video transmission part. I'm trying to confirm this.
I'm looking to understand the architecture that maps to the language they used.
They say they are just using LN as a "signal and control layer" and they hint at WebRTC, which I personally don't know much about.
If they were using that back-and-forth concept, the call would cost something denominated in sats/second (right?). They are framing the cost as as a sats/call number. If it does end up being sats/call, the lightning network would be at risk of seeing fees climb to pay for this bandwidth. It'd end up with the same problem as Ethereum -- fees climb to the level the marginal buyer can afford and bids, screwing the initial use cases. And, plus, it'd be inefficient, and therefore slow/choppy-video.
All of their current language implies the two nodes communicate directly after establishing the initial 15-sat handshake.
write
preview
0 sats \ 3 replies \ @freetx 10 Apr 2022
It doesn't smell like they are doing that back-and-forth concept over lightning itself for the video transmission part. I'm trying to confirm this.
I don't claim to know how impervious is doing things, but you do understand that the way the LN network functions is based upon invoices, right? The entire premise of how messages are sent and routed are built on that concept....I'm not sure exactly how they could be routing 0 sat messages...minimally they need to pay node routing fees anyway....
reply
0 sats \ 2 replies \ @jeff 10 Apr 2022
based upon invoices, right?
Yes, absolutely. I get this. :)
I'm not sure exactly how they could be routing 0 sat messages
This is exactly why I'm assuming they are using some other tech, unrelated to LN, in order to achieve the 15-sat per call number (presumably after using LN to establish the "cryptographically secure data transmission channels"). We're on the same page.
don't claim to know how impervious is doing things
I'm looking for somebody, to guess at how they are doing it. The solution space feels small enough, and this community smart enough, such that we might get a near definitive answer via process of elimination.
Because...
video call = identity + handshake + video transmission
And, using LN, and the 15-sats, makes sense for handshake part but not so much the video transmission part. What tech are they using for the video transmission part?
If you don't know, or don't care to wager a guess...that's cool, maybe somebody else on SN could provide an educated guess. Or maybe, the Impervious team might even be lurking.
reply
30 sats \ 1 reply \ @nout 10 Apr 2022
The video transmission is most likely WebRTC. I would be surprised if they use different protocol.
reply
0 sats \ 0 replies \ @jeff 10 Apr 2022
Do you know if the WebRTC transmission traffic would need to run ontop of LN? Apologies if this is a dumb question.
I read wikipedia, and it's talking about two other protocols (SCTP over DTLS) for transmission, that I don't know/understand...it doesn't sound like it would need LN, after the initial handshake.
reply