As we all know, the true number of Bitcoins in circulation will always be some unknown number less than the total number of Bitcoins mined. This is not ideal. Wallets can be lost, deleted, or the underlying media on which they are stored on can be damaged beyond recovery.
Are Bitcoins in it for the long haul? Or are they just a five year experiment?
I'm proposing a solution: wallet 'heartbeats'. I'm not sure if it is technically compatible with the existing software infrastructure, but I think it might be. If we define a heartbeat as connecting to the network, then perhaps wallets should give a heartbeat at least every seven years in order to remain valid. Any coins in a wallet that has not connected to the network for seven years become invalid and are made available to be remined, by some method that allows for their easy mining. Because I don't fully understand the mechanics behind the software, I don't know if this is possible, but if it is, I believe the idea has merit.
You could have symbolic links between addresses and unix-like permissions.
As long as the symbolic link exists the BTC would be transferable remotely from address to address without the original wallet. Bye bye lost coins.
Unix permissions would also prevent the theft that occurred at MtGox by allowing you to block transactions not authorized by you. You would pre-generate transactions which would be filled in by MtGox. That is you would control MtGox from the client. MtGox would not be able to create transactions without your wallet being online and sending requests.
Problem, criminal?
I think I'll work on this. After JSON is fully the format of the system. At this point I can't navigate the code like others can.
Unix permissions: Receive, Send, Operate