I hope I didn't overload the word "hash" too much - this is as in the Perl sense (%hash, $hash{key}=value) rather than MD5/SHA1 type hashes. Tie your hash variable with this and becomes replicated over the network.

At the moment it is an in-memory object so more suitable for tracking state of a system rather than a permanent repository, but no reason why it could not use a disk-based backend and do initial state transfers with a separate channel (current implementation limits the full database to be ~1MB in size).

Resync after failure currently involves a full state transfer, but it could be adapted to checkpoint periodically and transfer diffs (quorum to avoid splitting the cluster would be advisable too). Also it uses multicast so it's more of a local thing rather than general internet use.