matt, try to wait a bit and then do getinfo again, see if the block count has increased. I get the issues you describe as well, but it's because my laptop is shit. When I use a better computer it seems to run well even during sync. Once the sync is finally done the wallet runs fine, even on my shitty laptop.

Unfortunately it's likely that the full node will never be able to run/sync better on older machines

Couldn't you simply process this manually at first? Someone sends you a bank transaction with their BTS name in the transaction message and then once every 24H you send out your gateway asset to the names and whitelist them. If a whitelisted name sends you your gateway asset back you just transfer the money to their account.

so far it looks like the same problems as the last release.  I can't get synced enough to broadcast.  the chain stalled out at 45 days left. over 2 gig memory usage.  high cpu consumption.  can't quit the program without a crash.  program unexpectedly quits without any messages.  various elements of the GUI freeze while others still work.

Try to go into the console and type 'getinfo'. The blockchain could still be syncing in the background even though the GUI shows you've frozen. If getinfo also shows you stuck on the same particular block, then you're probably on a fork and have to delete everything except your wallet folder in your appdata/roaming/bitshares folder (after back up!!), and then save and put in checkpoints.json from http://www.riverhead.org/checkpoints.json

If your computer is old you just have to wait a long time. You can check which block you're on with getinfo. After a couple of hours it should be synced and then the wallet will calm down and can run without destroying your computer.

Right now it'll take 3 blocks before a transaction with standard fee gets 1 confirmation, so transactions will get to 6 confirmations much slower than normal. Add to the fact that falling prices causes miners to shut down, but difficulty will stay high for almost another 2 weeks. This could cause transactions to get even slower. Slower transactions will likely be interpreted as a sell signal by traders, causing the price to fall more and more miners to shutdown and so on, exacerbating the death spiral further.

People have suggested that mining is so centralized at this point that they will likely coordinate to ensure difficulty can fall gradually along with the price. I really hope this will be the case. A hard landing would be really, really ugly for all of crypto.

Quote from: Rune on January 14, 2015, 08:53:57 pm

Sucks that ripple is just as dependent on bitcoin as every other altcoin, eh?

In what way is Ripple dependent on Bitcoin? That's virtually an impossible argument to make.

I assumed that bitcoin going down would make ripple go up, or wouldn't affect it. Ripple is so different from other cryptocurrencies that it surprises me that it still behaves like an altcoin when bitcoin goes down.

xchain isn't monsterers gateway, it's an independent project.

This is for Windows right? Any guide for Mac user? My paranoia kick in just after I read 'delete everything'. lol

Yes, it's for a (shitty) pc with windows 8. The macbook I tried it on seemed to get stuck the first time I installed the wallet, but after a reinstall it worked itself out .

The only thing you should ever worry about deleting are your private keys, which reside in the wallet folder. Once 1.0 is ready hopefully users will never be required to mess around with the files.

I think the people who are getting stuck syncing some 20-30 days back are somehow getting caught on one of the old forks that happened at that time. I've seen many people mentioning these kind of issues over the past couple of days, and have had it myself on several machines.

If you go into users/[username]/appdata/roaming/bitshares and delete everything except the wallet folder and then run bitshares 0.4.27.2, then in some cases it will work and fix itself. For some reason I kept getting the same problem even when I did this.

I finally got it to work by manually inserting an even newer checkpoint in my appdata/roaming/bitshares folder from www.riverhead.org/checkpoints.json

Just right click and save the document as checkpoints.json, then put it in appdata/roaming/bitshares. Delete everything else except the wallet folder so you only have the wallet and the checkpoints.json in the bithshares folder. Then run bitshares again. The GUI will often show as if it's stuck on a block, however this is just because the wallet is really slow on older computers, and the GUI is slow to update. You can go in the console and write 'getinfo' to see the latest block you are on. It takes a long time for the wallet to return this information so just be patient. After a couple of hours of syncing on my shitty laptop, I now finally have the whole blockchain and my wallet is operational (except for the constant crashes that hopefully are getting fixed with 0.5 today )