For hosting static data, it's trivial to build a distributed cryptographic system which is arbitrarily censorship resistant. The trivial way is to distribute a large file encrypted, then once it's widely seeded, publish the key. It's really hard to censor a short string, basically as hard as censoring an idea.
For transaction processing systems which need to be durable, I'd go with something with multiple levels of indirection on the network, using links which are locally secure for short periods of time. Sort of like tor/onion routing with hidden services.
You might still put your processing nodes in a concrete fortress of some kind, but they're basically anonymous data processing equipment. Use tamper-resistant technology and the worst that happens to them is denial of service.
The point of having a published high profile physical location (like Sealand) is to claim jurisdiction there, and thus get some legal benefits in interacting with other jurisdictions. To the extent that everything can be done on the Internet, you don't particularly need that.
For transaction processing systems which need to be durable, I'd go with something with multiple levels of indirection on the network, using links which are locally secure for short periods of time. Sort of like tor/onion routing with hidden services.
You might still put your processing nodes in a concrete fortress of some kind, but they're basically anonymous data processing equipment. Use tamper-resistant technology and the worst that happens to them is denial of service.
The point of having a published high profile physical location (like Sealand) is to claim jurisdiction there, and thus get some legal benefits in interacting with other jurisdictions. To the extent that everything can be done on the Internet, you don't particularly need that.