Live data from Hacker News

Opening the Filecoin Project Repos

filecoin.io

41–50 of 58 posts

Re: Opening the Filecoin Project Repos

#41
post #38

Earlier quoted context omitted.

The proof of replication provides assurance that for some given data D, a unique replica R is created for it. What you’re proving with the Proof of SpaceTime isn’t that you have some data , you’re proving that you have the replicas . Generating the replica is slow, so you can’t do it on the fly. I gave a talk recently that goes over some of this briefly: https://youtu.be/GZZ2G9bPXsM

you talk for 15s about it on that video. I will try to read the secondary paper on this... but doesn't look like it can protect against someone just generating hashes for multiple accounts from the same stored data. P and (the fake) P2 can both reply to V with perfectly normalized storage. But regardless if the protection works against bad actors, it definitely "works" against good actors if you take into account sto…

Take a read through Ben's PoRep paper: https://eprint.iacr.org/2018/702

Re: Opening the Filecoin Project Repos

#42
post #38

Earlier quoted context omitted.

you talk for 15s about it on that video. I will try to read the secondary paper on this... but doesn't look like it can protect against someone just generating hashes for multiple accounts from the same stored data. P and (the fake) P2 can both reply to V with perfectly normalized storage. But regardless if the protection works against bad actors, it definitely "works" against good actors if you take into account sto…

To generate a response to the verifier, you have to have your replica of the data in question. A replica (from proof of replication) is a unique encoding of the data that is quite slow to generate. If the prover isn't storing the replica, they will have to regenerate it before they can respond to the challenge, which takes a noticeable amount of time.

What scale is "noticeable"? Is it slower than "we're going to pretend the network is slow and send you 1KB/s until we generate the rest"?

Re: Opening the Filecoin Project Repos

#43

Earlier quoted context omitted.

To generate a response to the verifier, you have to have your replica of the data in question. A replica (from proof of replication) is a unique encoding of the data that is quite slow to generate. If the prover isn't storing the replica, they will have to regenerate it before they can respond to the challenge, which takes a noticeable amount of time.

What scale is "noticeable"? Is it slower than "we're going to pretend the network is slow and send you 1KB/s until we generate the rest"?

[deleted]

Re: Opening the Filecoin Project Repos

#44
This project (I mean IPFS) startet with a very interesting goal. Now it seems they have totally derailed and went the blockchain based virtual currency way. So sad. Instead they should have invested their energy into better integrating IPFS eg. into browsers.

Re: Opening the Filecoin Project Repos

#45

Earlier quoted context omitted.

To generate a response to the verifier, you have to have your replica of the data in question. A replica (from proof of replication) is a unique encoding of the data that is quite slow to generate. If the prover isn't storing the replica, they will have to regenerate it before they can respond to the challenge, which takes a noticeable amount of time.

What scale is "noticeable"? Is it slower than "we're going to pretend the network is slow and send you 1KB/s until we generate the rest"?

1kb is much larger than most hashes.

Re: Opening the Filecoin Project Repos

#47

Earlier quoted context omitted.

To generate a response to the verifier, you have to have your replica of the data in question. A replica (from proof of replication) is a unique encoding of the data that is quite slow to generate. If the prover isn't storing the replica, they will have to regenerate it before they can respond to the challenge, which takes a noticeable amount of time.

What scale is "noticeable"? Is it slower than "we're going to pretend the network is slow and send you 1KB/s until we generate the rest"?

I wouldn't be surprised if regenerating it a few times is more expensive than simply storing it once.

Re: Opening the Filecoin Project Repos

#48

This project (I mean IPFS) startet with a very interesting goal. Now it seems they have totally derailed and went the blockchain based virtual currency way. So sad. Instead they should have invested their energy into better integrating IPFS eg. into browsers.

Last I checked, FileCoin was just an incentive layer for IPFS, not a core part of the protocol. Close association between Protocol Labs and the Ethereum community doesn't inspire me with confidence, but as long as IPFS works without it, I'm happy.

Re: Opening the Filecoin Project Repos

#49

The fact that as a miner you have no control over whether someone stores illicit documents on your machine seems like a dealbreaker

The fact that as a maintainer of a website with user-contributed content, you have no [up-front] control over whether someone stores illicit content on, and distributes it from, your server, seems like a dealbreaker.

username checks out

Re: Opening the Filecoin Project Repos

#50
What stops a filecoin miner from storing all replicas to S3? If nothing, then why use filecoin at all? Economies of scale would dictate that the most successful filecoin miners would simply be cloud storage providers by another name (but paid in tokens instead).
Post reply on HN