I had similar idea a while ago, although it didn't involve bitcoins and I never actually acted on it.

How do you solve the problem of an evil storage node provider who detects that you're trying to recover a file from backup, blocks it and sends you a "transfer X BTC to my account to get your data back" email?

Files are stored in multiple places and Storage Nodes will be asked to send files on a regular basis, for example, to ensure there is sufficient redundancy for a given file or if the end user wants to sync the files to a new computer.

The storage nodes also have no knowledge of who owns the file or what the contents are. Combined with the fact that they'd immediately stop getting paid for the other files they're hosting, it seems like the ROI for one of those evil nodes is pretty negative.

Why, oh why did they put "select" before "from"? It makes auto complettion so much harder.

easier to remember that format, other sql formats are same order...

Exactly. We tried to stay close to the SQL syntax to a large extent although there is no relational storage underneath.

"New Features in the Next C++ Standard" doesn't work (deleted by user), anyone got working link?