Mesh networks have a critical problem that has yet to be resolved.  Mesh networks depend on wide spread participation to be effective ...

You have skipped a much bigger problem of mesh networks. They can only operate efficiently if the principle of locality applies to the nodes' communication behaviour. Otherwise, the nodes closest to the high speed internet access have to carry not only their own traffic, but also the traffic of all the other nodes in their downline. Unfortunately, internet traffic today does not meet that criteria.

btsx:pmc

Thanks again!

So... if I understand this correctly, there is one special TITAN key for each account, which is the one listed by wallet_list_accounts, and what I have done works only with *THAT* key? And any other keys imported into the account are *not* TITAN keys and can therefore not be used in that way?

(Just trying to understand what's going on here. I don't really care if I can recover that 1 BTSX or not.)

I have two wallets with one account each. One is meant for everyday use and has a registered account name. The other is more or less "cold", its account name is unregistered and I have imported my PTS private keys there.

Yesterday I wanted to transfer funds from my everyday wallet to the "cold" wallet. So I opened the cold wallet, dumped its public keys, then opened the "everyday" wallet and added the unregistered account name with one of its public keys:

(wallet closed) >>> open pts
OK
pts (locked) >>> wallet_account_list_public_keys pts.local
[{
    "hex": "035dc3a125cca19787b58b2ba8af5a056a322f62f006f3b440192e7c50704fec6e",
    "native_pubkey": "BTSX7YXcLiSCP4nZg4psBo8R9FscJTytHmXVj2mcLxG1Cv1y7BFrKa",
    "native_address": "BTSXMVZZy1WUMCXxtLimkCGERNpVkfT4YmK59",
    "pts_normal_address": "PazdTWzxRst9aei352AwD6QbdcLAaStcB7",
    "pts_compressed_address": "PqPoCfTNqDjF5Rd2Wavis47JMvCn6Cgx6u",
    "btc_normal_address": "144rKSJpfmw5nNuBhXX645AYPMuLiLtdDB",
    "btc_compressed_address": "1JU24amF57nBH9pB96Gsi2sF7fmxEY4uj5"
  },{
...
  }
]
pts (locked) >>> open pmc
OK
pmc (locked) >>> wallet_add_contact_account pts.local BTSX7YXcLiSCP4nZg4psBo8R9FscJTytHmXVj2mcLxG1Cv1y7BFrKa
Wallet automatically backed up to: /home/peter/.BitSharesX/wallets/.backups/pmc/pmc-20140925T130206-account_add.json
pmc (locked) >>> wallet_account_list_public_keys pts.local
[{
    "hex": "035dc3a125cca19787b58b2ba8af5a056a322f62f006f3b440192e7c50704fec6e",
    "native_pubkey": "BTSX7YXcLiSCP4nZg4psBo8R9FscJTytHmXVj2mcLxG1Cv1y7BFrKa",
    "native_address": "BTSXMVZZy1WUMCXxtLimkCGERNpVkfT4YmK59",
    "pts_normal_address": "PazdTWzxRst9aei352AwD6QbdcLAaStcB7",
    "pts_compressed_address": "PqPoCfTNqDjF5Rd2Wavis47JMvCn6Cgx6u",
    "btc_normal_address": "144rKSJpfmw5nNuBhXX645AYPMuLiLtdDB",
    "btc_compressed_address": "1JU24amF57nBH9pB96Gsi2sF7fmxEY4uj5"
  }
]

The last command verifies that "pts.local" in the "pmc" wallet uses the same keys as in the "pts" wallet.
For testing (luckily), I transferred 1 BTSX from pmc to pts.local:
pmc (unlocked) >>> transfer 1 BTSX pmc pts.local test
OK
pmc (unlocked) >>> wallet_account_transaction_history
TIMESTAMP           BLOCK     FROM                TO                  AMOUNT                  MEMO                                        BALANCE                 FEE                 ID     
==============================================================================================================================================================================================
...
2014-09-24T19:19:48 571251    pmc                 pts.local           1.00000 BTSX            test                           xxxx BTSX       0.10000 BTSX        c863a255
However, after opening + unlocking the "pts" wallet again the TX hasn't arrived. Blockchain is in sync. Rescan doesn't help.
What I don't understand is that blockchain_get_transaction shows a deposit to a completely different address:
pts (unlocked) >>> blockchain_get_transaction c863a255
{
  "trx": {
...
  "provided_deposits": [[
      "BTSXfPy1KbpGxb3iWw5AU8buTydCZXFA6WPi",{
        "amount": 100000,
        "asset_id": 0
      }
    ]
  ],
...
Any ideas?

Since China was mentioned I think it's the Great FireWall aka chinese government censorship.

btsx:pmc

Thanks!

Right there you solved the fraud problem. Let's say a farmer is faking the results he's tinkering with the sensors(there no way you can prevent that)so it will show that he's farming system is the most efficient. Now every farmer in the network will use that fake information but evidently it will not work. So how about, instead of paying dividends right a way the others farmers should confirm that information is genuine or not. Only if the information was working for say 30% of the farmer then you pay dividends. So in that way  there will be no incentives  to fake the results.

OK, so I register 1000 fake farmers and publish 1000 fake sensor results. Some of these will be successful and collect dividends. Rinse, repeat - my cost is near zero.