I'm using https://www.bitcoinvigil.com/ which is very slick but I may build my own equivalent of this at some point and shove the wallet.dat on all of my machines.
I can see this being useful as a canary to let you know someone has acquired unfettered access to your device, but it doesn't seem very practical for high value targets (who cares about $5 of bitcoin if there's far more valuable info to steal), or if the attacker decides to steal the bitcoin wallet file and only transfer coins a few weeks later after he's already taken advantage of the other info he got off the target device (and by then you probably already know you've been compromised anyway).
At best it's confirmation that you have been compromised, not evidence that you have not.
hive is an alternative to running something like bitcoin-qt, which uses a lot of bandwidth and compute to keep up with the bitcoin network.
hive is lighter weight, uses a different protocol which i don't entirely understand but seems well trusted and efficient. i use it and bitcoin-qt and distribute some of my BTC among the two.
I freely grant that the Map Reduce community and the whatever this does for the Bitcoin community are unlikely to land on each other's search terms, but maybe that's only a matter of time.
Alternatively, thank goodness the DNS TLDs have expanded so one could name their project hive.java and hive.bitcoin.
"There are only two hard things in Computer Science: cache invalidation and naming things."
https://github.com/hivewallet/
Personally, I would not trust a bitcoin wallet that advertises itself as "the fastest, easiest and safest way to use your bitcoins." That's a bold claim, and not one that responsible crypto developers should take lightly.
