3 ms·

So I guess for 32GB, it's: - Sealing: Done once. 3-4h compute on one CPU initially, plus 2-3 hours on a few CPUs. - Proof of space time: 10 minutes of GPU tim

So I guess for 32GB, it's: - Sealing: Done once. 3-4h compute on one CPU initially, plus 2-3 hours on a few CPUs. - Proof of space time: 10 minutes of GPU time per day. What are the latency expectations within the system when my node is asked for a Proof of SpaceTime? Is it feasible to keep the sealing data, delete the file itself, then spend ~5 minutes downloading the 32GB on my 1 gigabit/sec home Internet connection when someone asks me to do the Proof of SpaceTime, and return the Proof of SpaceTime in 15 minutes (5 min to download, 10 min to compute)? Thanks again for engaging with me here! It seems the compute time itself isn't a constant enormous cost necessarily.

whyrusleeping 7y ago
> Thanks again for engaging with me here! Of course :) > What are the latency expectations within the system when my node is asked for a Proof of SpaceTime? We want them to be as low as possible, but the practicality of getting messages included into a blockchain, and the high cost of running snarks means its definitely on the order of minutes, realistically in the tens of minutes. A few things to note, the Proof of SpaceTime happens over all of your sectors, not just one. So that ten minutes of GPU time per day is amortized across all of the data you are storing. > Is it feasible to keep the sealing data, delete the file itself... Yes, thats feasible if the file you are downloading is already sealed (note: sealing generates a piece of data unique to you, so wherever else that thing is stored is effectively your owned storage). This isnt really different than you having your data stored on a NAS box somewhere. What you cannot do is download the original unsealed data and hope to respond to the challenge in time, as that would require rerunning the expensive sealing process.

3 ms·

So I guess for 32GB, it's: - Sealing: Done once. 3-4h compute on one CPU initially, plus 2-3 hours on a few CPUs. - Proof of space time: 10 minutes of GPU tim

by paulproteus 7y ago

whyrusleeping 7y ago
> Thanks again for engaging with me here! Of course :) > What are the latency expectations within the system when my node is asked for a Proof of SpaceTime? We want them to be as low as possible, but the practicality of getting messages included into a blockchain, and the high cost of running snarks means its definitely on the order of minutes, realistically in the tens of minutes. A few things to note, the Proof of SpaceTime happens over all of your sectors, not just one. So that ten minutes of GPU time per day is amortized across all of the data you are storing. > Is it feasible to keep the sealing data, delete the file itself... Yes, thats feasible if the file you are downloading is already sealed (note: sealing generates a piece of data unique to you, so wherever else that thing is stored is effectively your owned storage). This isnt really different than you having your data stored on a NAS box somewhere. What you cannot do is download the original unsealed data and hope to respond to the challenge in time, as that would require rerunning the expensive sealing process.