Quote from: atomrigs on May 25, 2017, 09:01:26 PM

A raspberry can not handle it with this block#. You need to use a decent hardware such as i5 cpu and 8gb memory. Also use the provided data, otherwise it may take several months to catch up. Grin

Quote from: ltcnim on May 25, 2017, 07:46:19 PM

I just setup a new client with 1.4.1 on a raspberry pi3 i had sitting in a corner for a while. However, it will take a lot of time to catch up to the current block.
I tried to use the chain data provided in the previous post, but unfortunately it did not work on the raspberry.

The main problem is, that jpc only uses one thread for block verification. I can't remember if there was the possibility to use more than one core/thread.
Anyone knows?

cheers

Well, the current situation is a little frustrating. Since with 1.4 it's not possible anymore to allow rpc connections globally it's hard to support the network further. I've setup a new node on a vps, but my home IP is dynamic, so I would need to stop the demon, and add the new ip every 24h in order to mine against the wallet. But because of the insane amount of blocks, it takes around 30mins for the startup of the demon.

I will let the node run for a while and see if I can find a way around it, but if the coin is to be revived, there need to be some major changes. Higher blocktime to reduce the amount of blocks to be processed, an up-2-date bitcoin base etc. Best would be to write jpc from scratch and then allow the exchange from old jpc to new jpc.

@cvaky: Use 1.4.1: Best would be to build from git.