pull down to refresh
0 sats \ 7 replies \ @random_ 21 Apr 2022 \ parent \ on: cjb/GitTorrent: A decentralization of GitHub using BitTorrent and Bitcoin bitcoin
Yea, I was looking at a hackathon project for torrenting over lightning and it has a similar trust problem as you described.
Maybe the security issue of reusing a preimage can be made into a feature? 🤔 You can settle an invoice if you know the preimage, right? What if the preimage were a chunk of the data you were interested in?
Can you elaborate on how you think that might work? There might indeed be some hackery with preimages, which is really the only way a layer 3 can hook into Lightning.
reply
There's trade-secret, but I'm not sure how it works.
By paying an invoice, you are essentially buying the preimage, right?
Request hash of the data you want from nodes who signaling they are seeders.
They make an invoice using the hash of the file or a chunk of the file.
The preimage is revealed when you pay the invoice.
Nodes routing the payment would be incentivized to store these preimages, too, if they were revealed to them. (This relates to what I was saying about preimage reuse.)
Searching for seeders with they data you want could work similar to lightning escrow.
reply
deleted by author
This is one reason I'm so concerned about lack of proof of payment in AMP/LL's implementation of static invoices. How do you build a decentralized layer 3 without being able to prove that things happened on layer 2, without "hooks" into layer 2?
Anyway, the best hackery of preimages I've seen has been done by @03bcf114f6 on squeaknode and he ran into some pretty big hurdles.
reply
deleted by author
deleted by author
deleted by author