A new player in the low power wireless communications realm is soon to hit the mainstream, so they say. I've been waiting for years for a ZigBee enabled Android phone, but it's never come to pass. I don't want some clunky add-on device, so I have been waiting. Near-field magnetic communications aren't as sexy to me, but if a light/mobile client is developed that can use Dash7/WiFi/NFC to connect to any other such device for direct PeerDevice-to-PeerDevice transfers, automaticly or on command, then real world bitcoin transactions can become commonplace regardless of how readily available the Internet is for a particular buyer and seller at a particular time & place. The client could automagicly attempt to update it's blockchain anytime an open WiFi hotspot is available (and the user is willing to drain the battery, wifi is a battery killer on a smartphone). Yet, DAsh7 is intended to be slower, but with significantly
less power; so a Dash7 radio inside a cellphone can reasonablely be left on under normal daily charging conditions. (not everyone will do this, but many would) So a client could passively query the Dash7 devices that it could reach every minute or so, and finding new ones, could attempt an update in either direction. At a max transfer rate of 250 kbs, this wouldn't often be quick, but would keep even those smartphone users without any data service relatively up to date if they frequent public places. Powerusers on the train would spend the better part of their commute updating the clients of the less well healed users, without ever knowing or caring that the trade has occured. The same for trips to the local pub, the ball game, or any other place wherein the public mixes anonymously for more than a passing few seconds; airport & hotel lobbies, resturants, any kind of theater, etc. Even during a widespread loss of connectivity event, such as a city power outage, Dash7 enabled mobile clients should be able to transact with just about anyone, and still mix the record of the transaction across the city population in such a manner that odds are high that double spending would be extremely difficult, and the odds are also high that the transaction will find it's way to the Internet and back to the main blockchain before the sender does. Dash7 also has the potential to become a form of 'citizens band' version of instant messaging, with the advantage of intended encryption, and rather than pay way to much for text messaging services for cell phones that they rarely talk upon, teenagers might move en masse to Dash7 enabled devices. Due to the encryption, the 'bursty' data design, and the automated nature of Dash7; the datagrams might not be distiguishable among a crowd even with nation-state resources. Said another way, although an agent with the right equiptment and resources could record every Dash7 transmission in any given area, there might not be any way to definitively distingish the datagrams of a bitcoin client from a Dash7 PeerDevice-to-PeerDevice message forwarding client.
I can't find any holes in this plan, but I'm admittedly narrow focused when I'm new to a promising technology. Please, if anyone can find errors or other issues with this, poke some holes in my ignorance.