> especially if, say, someone has infrastructure issues or decides to stop participating and removes their capacity? The network uses Reed Solomon erasure codi

> especially if, say, someone has infrastructure issues or decides to stop participating and removes their capacity? The network uses Reed Solomon erasure coding to prevent against failures. You can pick your own redundancy scheme, but the default is 10-of-30 today. (3x overhead). > Does the system allow those specific encrypted blocks to be removed Hosts have the ability to remove specific blocks if law enforcement informs them that they are storing illegal material. The host must make the choice to remove it though, you can't just choose to take down data. > How do you protect against correlated failures - i.e. does separate hosts rule out the same person operating multiple servers? Any geographic requirements so the same power outage, hurricane, etc. doesn't take out multiple copies? A combination of proof of burn and ip address lookups help us guarantee diversity.