If the price lowers, I'm going to want to use it to store files instead of my hard drive at home, right? Can you share links with other people to fetch files?
If the price gets higher, I'll want to buy more hard drives for more people to pay me to use my space. Is that how this works, or am I misreading?
If it works like that, it's pure genius. You'd be able to get a lot of use out of it without ever converting it. This is a weird thought, but: could filecoin prop up the value of bitcoin, because the only way to convert filecoin to and from hard currency would be through bitcoin?
edit: Could I boot from this? Could my phone boot from this?
edit2: I'm assuming that the race to claim the proof reward will encourage low latency retrievals. Would I be able to tune my client in order to choose my own balance between latency and security, for example only rewarding quick responders but paying them highly to encourage a more low latency mix? Would that open this new cloud disk space market to quant trading strategies?
edit3: If latency matters, then network topology matters. Different places on the network would be more lucrative than others.
edit4: I'm seeing a workflow where I buy a hard drive, partition it into a local partition and a filecoin partition, then open it up to the network. After a few days, my filecoin partition is full, and I've generated a lot of filecoin. I use that filecoin to start copying files into a mounted virtual filecoin filesystem. I can rsync between local filesystems and filecoin filesystems.
I could actually delegate all of that activity to a single fileserver at the edge of my home network, and have all of my home computers mount files from that (and phones and home automation could call home to it too.)
- Filecoin is not a filesystem. The whitepaper doesn't even talk about the technical implementations of storage. Filecoin focusses on "how to retribute peers" more than "how to store data".
- Filecoin is supposed to be used on the network
- Filecoin is supposed to be used in a cluster of mutually distrusting peers, who by the power of the oldest and most effficient incentive ever (aka money) can come to an agreement that is beneficial to everyone.
Given these, I wouldn't advise you replace your hard drives with it, not even your home computers; high latency should be expected. OTOH, Filecoin is the way to go if you want to backup your whole TBs of data without paying thousands of dollars each month.
Note: I only speak from a very quick glance at the whitepaper. When I see something like that I always rush to the technical explanations, and I was a little bit sad that it only talked about the coin aspect...
I wasn't thinking that Filecoin was a filesystem, but that a filesystem could be built on top of filecoin. It turns out that what I'm thinking is probably what MaidSafe[1] is doing.
This is pretty interesting from a economic standpoint. The USD price for file space would likely hover around the same price of something like S3. If the price paid by the user is too high, they are better of using S3 for storage. If the price paid to the user is too high, it creates an arbitrage situation in which someone can simply use S3 to host Filecoin data. This should theoretically provide more stability to the price of Filecoin in comparison to other virtual currencies which is simultaneously the biggest strength and weakness of most of these things.
Filecoin providers may feasibly beat S3 on price in USD if (i) they're betting on the protocol because up-front losses may be more than compensated for in investment returns on Filecoin or (ii) the alternate for them is making no money on unused disk space.
The problem is that the investment possibilities for Filecoin might be limited since it will be tied to a real world service unlike most other digital currencies. People are free to speculate how much Bitcoins are worth because there is no company out there saying "Bitcoin are worth X". Filecoin will basically be saying "Filecoins are worth X GB per hour". The way to combat this issue is to tie the price to some other currency (e.g. X USD or Bitcoin per GB per hour paid in Filecoin), but it would be tough to convince other people to use your currency if you aren't even confident enough in it to price your own products using it.
For your second point, we need to keep in mind the free space might be empty but it is not free as in beer. Using the disk will cost extra electricity and CPU cycles. Plus we shouldn't forget that disks are still the most common piece of hardware to fail inside a computer. Increasing usage of that disk increases the risk of failure.
>The pricing is left fluid precisely to avoid this. The price can change over time. 1 Filecoin / N time today. 0.1 / N tomorrow.
That makes sense from an economic perspective but how does that work from a customer service perspective? Is the price pegged to a different currency? How would a user be able to predict the cost of the service if the price is not pegged to anything?
How can you predict the value of a dollar? It's not pegged to anything either.
Although in fact the decline of the value of the dollar is relatively predictable because of the Federal Reserve's policy goal of keeping inflation relatively low and the law of large numbers as applied to the generation of the real rate of inflation.
At my local deli a dollar used to buy a bagel with the works; and now buys less than half of a plain bagel. That's over the course of 20 years. Any unit of exchange is valued anew in each transaction; the persistence and trends in value exist mostly due to social pressure and the cost of bargaining. I don't make offers and counter offers on each bagel I buy; I just look at the sign and accept the price or leave without a bagel.
> Although in fact the decline of the value of the dollar is relatively predictable because of the Federal Reserve's policy goal of keeping inflation relatively low and the law of large numbers as applied to the generation of the real rate of inflation.
That's a crucial point. If the Fed didn't pledge to keep inflation under control, the dollar wouldn't be such a great store of value or medium of exchange. It's the stability promised by central banks that allow you to "predict the value of a dollar" in the immediate future.
If Filecoin works, the price to store, say, 4 TB of data will be bounded by the cost of a 4 TB disk and the cost of 4 TB of S3. That's a wide range, but it's not as bad as Bitcoin's 1000% fluctuations.
>The problem is that the investment possibilities for Filecoin might be limited since it will be tied to a real world service unlike most other digital currencies.
That certainly hasn't dampened the investment possibilities in actual, government-issued currencies.
> The way to combat this issue is to tie the price to some other currency (e.g. X USD or Bitcoin per GB per hour paid in Filecoin), but it would be tough to convince other people to use your currency if you aren't even confident enough in it to price your own products using it.
You can't peg a decentralized currency. You need to be able to control supply in order for the peg to work (ie. to sell more into the market to lower the price, if needed), and then it wouldn't be decentralized.
What if both the price paid by the user and thus paid to the miner is lower than S3, how would you arbitrage that? What would drive the price up to s3 prices? Scarcity?
There wouldn't be a direct arbitrage opportunity if the price was lower, but we have to remember there is a reason why S3 has been so successful. HDD space and CPU cycles aren't free. Plus there is the redundancy issue that others have mentioned. Amazon can help address this because they control the servers and can nearly guarantee their uptime. Filecoin doesn't mention any requirement of uptime for its users, so it will likely need to combat the problem by just throwing numbers at it. We then have the user's costs (electricity, wear and tear on their machine, and opportunity costs of doing something else) multiplied by whatever number Filecoin feels is enough to guarantee redundancy.
This is a long way of me saying I am not sure how much lower than S3 pricing they can realistically accomplish.
This is an amazing business model. If they can make it user-friendly (big if) they'll essentially be offering a more cost-effective, more robust alternative to Dropbox.
This appears to be truly disintermediated (P2P) secure file sharing?
If well configured, the system should be fault tolerant (i.e if any node drops off the network there are other copies available elsewhere. Many systems already implement this (including Bitcoin itself). To be more robust than Dropbox, all you have to do is have more system uptime than AWS (or whatever service they're using to store all that data).
One of the things that people tend to underestimate is datacenter outages. When an Amazon datacenter goes down it takes out many sites with it. We're working toward a world where data is redundantly kept in many different datacenters/locations. In those almost-total failure cases, latency is better than no availability.
Cheaper and more robust isn't really what Dropbox has been competing on.Great UX, feature set, support, and general marketing is what will make the difference.
Of these I think UX is the most significant. UX is where the proprietary walled gardens and centralized services always win.
Good UX is unbelievably, grindingly hard. If you want to make a product with a good user interface and overall experience, 90% of the work is going to take you about 25% of the time and the remaining 10% is going to take you 75% of the time. Most hackers decide a product is done when it works, but in reality they're not even half way there.
Apple is probably the overall king of UX. If you look at their process and their culture, they obsess and obsess over tiny little details that are irrelevant to core functionality as understood from a purely technical point of view.
Closed silos have a clear revenue model. That enables them to invest in pushing product quality and user experience the rest of the way, past where hackers and enthusiasts would take it and into the realm of polished usability that real customer bases demand.
Who's going to pay entire teams of designers to obsess over the filecoin.io client's "experience"?
Mastercoin pays its developers using currency created in the first block, in a system of bounties managed by the Mastercoin foundation. You can contribute a patch and get paid. Go read on their website, it's interesting.
But it's absolutely not more robust! What if all the 'servers' having your files go into limbo at once? Dropbox will make a big splash and you know who to go after, but with filecoin you're on your own. :-)
Well Dropbox/Gdrive/Skydrive etc. all offer free storage in the range of 15-30gb, which is enough for most normal users. For professionell use there is S3,glacier, box etc. and they all offer known security and redundancy.
Most businesses won't touch anything related to bitcoin and things lacking a reliable SLA.
While a lot of people have unused storage space, many lack usable upload bandwidth and have low availability, so I would assume a lot of copies would be needed.
It's gonna be very interesting to see if stuff like this or storj, which was posted earlier today, can compete with current services.
But as someone with a lot of servers with unused space I sure hope so.
One has to wonder how much unused disk space is sitting on the generic Dell boxes in various cubicle farms, libraries, etc. Could be decent trickle revenue, and it wouldn't impede usability/performance the way mining does.
Lots of businesses are already relying on Bitcoin for revenue. The reliability -- and other properties -- of a network like Filecoin can be measured easily. Businesses are all about numbers. :)
Maybe I've missed something, but how does Filecoin handle redundancy, and how does Filecoin handle delegation?
The devs seem to hope that by making the rare pieces valuable, they will somehow avoid having low redundancy. But what happens when everyone joins a large pool like Ghash.io, and every file has only a single point of failure?
I would not trust my data to Filecoin, it seems too easy for files to get permanently lost. There are no guarantees that every file piece will be managed by at least N nodes.
Great questions :) -- this borders into future announcements, so sadly I'll have to defer to the answer on this paper, which you summarize well here. (Not asking you to believe, only to wait a bit longer.) Also, this answer is actually not bad: information on the distribution of pieces will become widely available so users can tune rewards accordingly. Storage pools also have a ceiling: after backing up the entire piece set, it's better for them to compete than to keep growing.
After backing up the entire piece set, the requirement per-node for joining the pool declines - say 100GB each instead of 500GB each. Or perhaps you have a setup where the pool master takes care of storing all the data and the workers all do POW. Then it's up to the pool to tune prices so that workers can profit as much as possible.
You might end up with multiple competing pools, but it puts the barrier-to-entry of being a new pool at a high price. Everyone will mine for the cheapest pool, and the 1 pool that can provide all the storage at the lowest cost is the 1 pool that will control all of the data on the network.
In equilibrium, people will still compete to avoid sharing the reward with others if they can avoid it. You don't need a full pool to have high expected reward. Anyway, stay tuned ;) (+ for getting rid of PoW altogether).
Maybe you could also expand to also allow poeple to mine by running a distributed search engine. So they can basicly decide wether they offer simple storage or storage + processing power + low lattency.
Store redundant copies yourself, each copy encrypted with a different key.
If there are a lot of storage nodes competing on price each copy should end up on a different node, and none would be able to afford a centralized storage service.
So it sounds like the incentive model is kind of fundamentally broken. Is it correct to say that miners are incentivized to A) store trash data in a way that lets them mine with zero actual storage backing it up and B) consolidate their storage into the same hard drive, until there exists only a single copy of the data on the entire network?
Yes. Their counter argument to (A) that the trash data will cost more to store than the user gets for retrieving it (though this isn't true if the attack is successful and results in them being the only miner/retrieval server), and (B) they don't seem to consider a problem.
There are other issues— e.g. arbitrary data can be censored and the only harm is lost mining revenue proportional to the censored data. (e.g. you could censor 0.1% of all data, and probably make every file unreadable (just by censoring the first word of it) but only be unable to answer 0.1% of the file queries).
I don't really see the point— having a file storage service that you can pay for with cryptocurrency make sense, but integrating it in this manner seems to serve no technical purpose other than to fuel investment speculation and otherwise just makes the system worse.
Is there a way to host a file for 1 month, 2 month, 1 year.... by paying more/less (and maybe increasing the storage time by additional payments). That would be the right model that could translate to S3 storage with the same price. Without a time component, storage prices have strange meanings.
I'm surprised the whitepaper didn't cite PermaCoin [1], which addresses the same problem with proofs-of-retrievability and uses the BitCoin blockchain for storage. Would the authors like to comment on how their work differs?
We designed Permacoin with the goal of being rigorously secure. Our design addressed a bunch of problems that aren't (yet) addressed by filecoin.
- Erasure coding (over the whole dataset) guarantees that you can't just drop some of the filed and make them unrecoverable.
- Preprocessing the entire dataset to be full entropy guarantees that it isn't cheaper to store one portion of the dataset than another (for example a segment with just all zeroes).
- Outsource resistance: it would be a shame if someone just runs a cloud service to store the file, which would be more efficient than using local hard drives. Arguably this is already happening with Bitcoin cloud mining. Permacoin and the follow up work on nonoutsourceable puzzles address this.
Without these features, the concern is that selfish miners might find ways to earn more filecoins without actually providing the useful service. Incentives are correctly aligned only when there's no way to game or cheat the system.
Filecoin provides a richer interface (get and put for individual files) than Permacoin (which only guarantees recovery of the whole dataset at once). We would have supported this interface if we could figure out how to, while maintaining the same standard security properties! This is difficult (but hopefully possible) future work.
On the other hand:
- Maybe it will be a long time before practical ways to game filecoin catch on.
- if filecoin builds a community that values altruistic participation like Tor (and even Bitcoin to some degree) it will be useful anyway
- it could be possible to improve filecoin with features from Permacoin
- there's a lot to learn from the actual launch of a system like this with real users
Hey, yeah. I found out about permacoin (which is great!) after designing this construction. Turns out that permacoin and filecoin are really compatible, and complementary. amiller and I will be talking about it in the near future. (btw, permacoin's non-outsourceability is a great contribution! it should also be added to regular bitcoin)
And, to answer your question, I didn't cite permacoin here because I would have to address a whole range of things like how they overlap/differ/which one is good for what parts. Perhaps I should've, but I think it's best left to a future paper (hinted at in the discussion). Stay tuned! :)
I hope you can take more hints from permacoin. There is an important economical point in permacoin's whitepaper:
"The expected reward per unit of work is approximately constant, even for very small investments of computational effort. This prevents large participants from monopolizing the system and driving out ordinary participants."
Maybe I don't have a deep understanding how filecoin works, but as far as I know if you don't have the storage capacity which can even reach the current difficulty then you have an expected reward of 0. Maybe it's a non-issue and the difficulty will never reach let's say 10MB, but if it reaches 1TB then it will be really hard to hop in the mining business.
Filecoin uses what they call "proof-of-retrievability".
The thing about proof-of-work is that it is a proof. Assuming that sha256d is unpredictable, you will on average have use a certain amount of energy to find a low hash value.
With proof-of-retrieval, the name itself is lying. There is no way to prove that a piece of data went from one person to another. It should be called invoking-trust-in-retrieval-and-proof-of-having-the-file.
Along with that, because hashes have the property of being irreversible, blocks can be hashed and the winner cannot change the block without doing work again.
Because of these properties, filecoin must use PoW (which their whitepaper states they do).
According to their whitepaper, you must first construct the proof of ownership in the file, then you perform the PoW with that seed.
This leads to huge economies of scale because the startup cost of mining at equilibrium will include storing an abundance of files (probably all of them).
> There is no way to prove that a piece of data went from one person to another.
Actually, you can prove that a piece of data went from one person to another, but others in the network must also have a copy. I was thinking a few months back about applying a similar idea to Bit-Torrent / P2P sharing. It was possible to prove that the file was sent given that all nodes had a copy of the file; so the idea is more feasible for file sharing than it is personal file storage.
> This leads to huge economies of scale because the startup cost of mining at equilibrium will include storing an abundance of files (probably all of them).
I was following until that line. Why 'all of them'?
This is neat. I did some work on a data storage platform through a bittorrent tracker/community back in 2010. There was no concept of a currency instead relying on the tracker to prioritize downloads since nobody would have any incentive to download any particular file. The more you stored, the more you could store.
It's neat to see this concept popping up now, http://storj.io/ is another platform that popped up recently.
The authors address Sybil attacks in the paper. Essentially, there is a PoW style consensus using hashes of files+metadata (as opposed to bitcoin which is hashes of nothing + metadata)
I'm at work and don't want to read either of the papers at the moment, but if A asks B to provide proof of having stored some bytes, could B proxy that request to C and replay the reply to A ?
FWIW, thats usually called 'delegation' or 'outsourcing'. Apparently it's intentionally not resistant to this (sounds like a pretty bad idea— IMO, but apparently intentional). See the IRC log I linked above.
As long as a node you control has the data and can retrieve the file, I don't think there's a problem. If you could proxy the "proof of retrieval" than you could surely proxy the retrieval itself. Pooling resources shouldn't break anything.
But you could make it look like several computers have copies of the data when there's really only one copy of the data. You would get credit/coins for multiple copies and reduce the redundancy of the files.
From what I read in the paper, it sounds like you _don't_ get paid for providing the data. You get paid for proving you have it when mining a block. Distributing your storage across multiples nodes would simply make it easier to "mine", but wouldn't get coins passively. That is, if I'm understanding the protocol correctly.
No, files are contributed to the network as a whole, must be distributed, and require payment. See the discussions on mining and on rewards in the paper: http://filecoin.io/filecoin.pdf
Ok, I see some similarities to other projects here. Let's introduce one additional layer of abstraction that we call "resources-coin". Disk space is not the only limited resource that can be shared using an economic system; CPU cycles (not for hashing, but doing actual work), network bandwidth, storage space (like this project) are all things that have some value that one can be rewarded for. I bet there are many more ways.
The difference with traditional bitcoin is that, we're not talking about an absolutely limited resource here. While bitcoin will stop growing at a certain point, no matter what happens, storage space on earth will always grow. So will the overall bandwidth, overall computational power etc.
And that is why these things are not going to work on the long term. You cannot build a currency based on reward.
These things will work, they just won't be good for "store of value" like bitcoin. Supply of disk space, bandwidth etc keeps growing, but the demand for those resources grows as well. Hard to predict the ratio of supply to demand, and therefore the price, but I think they could work very well in the long term. Not as a universal payment currency, but rather as a token (with fluctuating price) for some particular type of service.
I see the future of "resource coins" as being efficient mechanisms for p2p resource distribution. Conventionally, a customer would use their credit card to pay some cloud hosting company. The conventional hosting company is a business which operates as a privately managed bureaucracy. A P2P coin operates as standard protocol acting as a meta-company, aka a DAC/DAO - Digital Autonomous Company/Organization.
In a conventional business, a private bureaucracy manages a resource uses it to provide a service (bandwidth, disk space, and CPU as managed by a hosting company). P2P coins replace that centrally-operated middle man with a decentralized algorithm and account database. Bitcoin is like a meta-company which operates a distributed ledger internet payments. Why stop at payments? If its efficient, we should *coin all the things.
"I see the future of "resource coins" as being efficient mechanisms for p2p resource distribution." -- Agree. This is totally valid and can definitely work; it's kind of a special purpose currency or intermediate currency then. Just a way to measure the value of a service, like storing stuff.
I'm still not convinced that you could actually use that revenue as a value in itself, like, storing it for later use. To be fair, I did not read the paper. If you would get existing coins for sharing a resource, that could work ... if you only rely on the mining process to earn value, it won't.
Unrelated to Filecoin, this brought to mind a question about the Bitcoin blockchain I've been pondering recently.
Since users can put small arbitrary byte data in a transaction that gets included in the block chain (AFAIK), isn't it possible that an attacker could insert illicit / illegal data that everyone using Bitcoin replicates?
Copyrighted materials, sensitive personal information such as SSNs, and moreover, child pornograpy immediately come to mind as things that could forever be persisted.
If this is possible, wouldn't that make everyone using the bitcoin blockchain criminally liable for storing and/or transmitting that information? (In the US and similar jurisdictions.)
I assume lightweight clients that only store a hash would be unaffected. But still, this seems like a serious issue.
Yes, it's been known for a while that people can upload illegal bits into blockchains. Don't think transaction steganography would hold up in court though. You could do similar things with DNS records, etc.
File storage services though have the added concern that they're specifically designed to distribute files. Filecoin addresses this by (a) encouraging everyone to pre-encrypt before adding, and (b) creating a fluid market based on incentives. Nodes aren't required to store every file, only strongly incentivized to do so. Nodes are free to follow strong counter incentives (say, a well-known list of "illegal hashes" published by authorities).
In reality, the way many courts handle things like this is to target the entry points: the websites advertising which are the illegal hashes and how to get them. (e.g. the piratebay instead of bittorrent inc.)
It certantly easier to make a complicated case the broader the data channel is— so this is just one reason (along with scalability and cost-of-decentralization) that Bitcoin is pretty stingy with sidechannels.
Make encryption at source compulsory (since the data is uploaded through your software) and no need to tell the user about it. rather advertise it as a feature.
I agree, this would be the best action for both the user and host. I'd add a check on the host to make sure the data looks random as well to protect against rouge or malfunctioning clients that attempts to store plain text. Encryption must be mandatory and enforced, this will prevent so much pain for all parties.
Here's a good example of it so far[1]. That address was chosen to have a hash that comes out as the bluray aacs key, forever preserving it in the blockchain. There's some other ways it could be done but this is one really simple way to start.
The more serious issue that I pondered with a friend was injecting a small malware stub into the blockchain. If you have a copy and an antivirus, Bitcoin could go haywire.
It wouldn't be too expensive, given there are <6kb stubs that are detected by many antivirus companies.
Unfortunately https not working, because they are using github pages. They should really put up a https site especially considering they are a crypto project and are soliciting email addresses. At least a TOR hidden service or a namecoined https site.
What I think would be a limited factor is the bandwidth: You need at least 35 megabit per second for streaming full HD video+sound ...
While most people are stuck on 5 Mbit Internet or 50 GB/month quota.
I'm hugely optimistic about the market for "proof-of-application" cryptocurrency since it's also the next step in "race to the bottom" - make use of the spare resources of all our commodity electronics and eliminate a centralized authority simultaneously. We've had plenty of peer-to-peer systems, but the incentives are mostly wrong to make them scale up past the niches of the black market and political radicals.
I always wanted proof of work to be computation power which is saved up over time, which can be spent as computation bursts on a network, or sold. Perhaps using pnacl binaries to to the computations.
Rather than waste CPU power on mindless hashing, you could accomplish real computation tasks.
"Proof of Non-Work" would be a very interesting concept, although I can't think of a way to do it. (In a sense, Proof of Work is an expensive method to accomplish Proof of Non-Work.)
Yes. Filecoin uses proof-of-retrievability i.e. you prove that you can access arbitrary parts of a file without needing to always provide the whole file.
Hmm. Does this mean that the cost of storing new data over time will grow, to support the larger and larger amount of existing data that needs to be stored?
Users pay to Put data into the network. Are there any ongoing payments for storage? I don't see any way to delete data either. If the network promises permanent free storage after a one time fee, it's sure to fail eventually.
"Transaction issuers must pay for all rewards up-front"
Will there be a way to make ongoing payments for data retention? With a proper API this could be used for secure distributed backup, that would be a killer use and something I would gladly pay "miners" for.
The way I understand it, Get'ing the data also publishes it to existing miners, so they can start storing it if it's a piece with a high reward value. The TTL is decreased by the Get operation, though. By understanding how valuable your data is you can choose a time to Put it again (while reward/TTL > market rate) with a new reward attached. Obviously that reward/TTL should be higher than the last one to buy you a bunch of safe Gets again.
Storj doesn't make any technical innovations, their plan is essentially "make some nice looking web apps and let other people worry about inventing the things we need". Storjcoin is a standard blockchain, but actually isn't even neccessary at all.
Filecoin actually addresses the technical challenges in building something like this, and maybe Storj will end up using it in their stack.
I spoke with super3, the Storj founder earlier today, and he was going over how they'll go about providing Proof of Storage. I'm not qualified to explain it myself, but expect a revised whitepaper in the next couple weeks that goes over it in detail.
At first glance the concepts may seem similar, but this is a different thing altogether. Storj is a service layered on top of other blockchains. Filecoin is a new blockchain protocol itself, with its own contributions: mining construction, use of proof-of-retrievability, put/get as transactions, and more. Read: http://filecoin.io/filecoin.pdf
Both smell like a scam, "coincidentally" today storj started fundraising by getting people to send them bitcoins for useless storjcoins they created, the worst part is people falling for such a scam, then again there's a fool born every minute which is a business model a lot of companies rely on.
In this case and in storjcoin case the actors behind it all remain anonymous
I can understand why -- with all the scams out there -- that would be one reaction. But note that Filecoin makes important technical contributions on top of the Bitcoin protocol. You can read the paper here: http://filecoin.io/filecoin.pdf
FWIW, we aren't really anonymous. Neither in the storj case (you can find who they are in their website), nor in the Filecoin case. (hi!)
The Storj developers aren't anonymous at all...Their names and photographs are posted in their pitch deck, and they're active on reddit. The Storjcoins won't be useless either; they'll be the native cryptocurrency in their apps, and from what I understand they intend to add the ability to send data directly to an address in the future.
Can an individual node enforce that only encrypted pieces are allowed to be stored on their hard drive? If not, a hard fork could be introduced to enforce this and provide everyone with plausible deniability (like tor relays).
Does "Renting your spare room" (airbnb) or "Renting your car" (uber) sound sketchy? It's all about how the protocol works and the security guarantees on top. Users should store pre-encrypted files. (except for public goods, like wikipedia)
If the price gets higher, I'll want to buy more hard drives for more people to pay me to use my space. Is that how this works, or am I misreading?
If it works like that, it's pure genius. You'd be able to get a lot of use out of it without ever converting it. This is a weird thought, but: could filecoin prop up the value of bitcoin, because the only way to convert filecoin to and from hard currency would be through bitcoin?
edit: Could I boot from this? Could my phone boot from this?
edit2: I'm assuming that the race to claim the proof reward will encourage low latency retrievals. Would I be able to tune my client in order to choose my own balance between latency and security, for example only rewarding quick responders but paying them highly to encourage a more low latency mix? Would that open this new cloud disk space market to quant trading strategies?
edit3: If latency matters, then network topology matters. Different places on the network would be more lucrative than others.
edit4: I'm seeing a workflow where I buy a hard drive, partition it into a local partition and a filecoin partition, then open it up to the network. After a few days, my filecoin partition is full, and I've generated a lot of filecoin. I use that filecoin to start copying files into a mounted virtual filecoin filesystem. I can rsync between local filesystems and filecoin filesystems.
I could actually delegate all of that activity to a single fileserver at the edge of my home network, and have all of my home computers mount files from that (and phones and home automation could call home to it too.)