I would like to see a market pegged currency that is based on the gross world product (GWP) per capita. (GWP is the same as global GDP. See "Gross world product" on wikipedia)

1 BitGWP = (GWP)/(global population x 10,000)

Which means that the average human spends the equivalent of 10,000 BitGWP per year.

If GWP per capita goes down then the value of BitGWP would go down, encouraging people who hold it to spend. If GWP per capita goes up then the value of BitGWP would go up, encouraging people to save. If BitGWP became a significant enough part of the economy it should have a stabilizing effect, encouraging spending in lean times and saving in good times.

Wikipedia says that in 2012 the purchasing power parity per capita GWP was US$12,400. That means that in 2012 BitGWP would be worth ~$1.24.

What would it take to get something like this implemented?

I looked in the logs. I found a lot of "error fetching key 679837", "Exception thrown while canceling message_oriented_connection's read_loop" and "Peer IP is disconnecting us because: I rejected your connection request (hello message) so I'm disconnecting"

I would post a larger sample of my logs, but when I try the forum says "Sorry, you are not allowed to post external links."

Version: 0.4.22
OS: Windows Vista 32 bit

My wallet synced up to block 679840 and now won't connect. I have tried closing the program and opening it again. At first it says that it has 8 connections, but doesn't get any new blocks. After a couple of minutes it switches to "Not connected".

Also, it oddly seems to be actually losing blocks. First it said that the latest block was 679840. After a shut down and reopen it said that the latest block was 679839. Another shut down and reopen and it now says that the latest block is 679838. 

I've tried deleting the peers_leveldb folder as suggested in this comment: index.php?topic=10185.msg133395#msg133395 That didn't seem to have any effect.

Edit: This has been resolved.

I got help with this on github. Here's what was happening: A memory leak was causing the wallet to use increasing amounts of RAM. When the RAM use became too much for my computer Bitshares crashed, corrupting the database. The corrupt database kept the wallet from connecting or accessing the blocks it already had.

Version 0.4.24 fixed the memory leak. Deleting the blockchain database and resyncing fixed the corrupt database.