Quote from: jc12345 on July 03, 2015, 10:30:23 AM

Quote from: Belligerent Fool on July 03, 2015, 10:15:37 AM

Quote from: dukester99 on July 02, 2015, 03:31:52 PM

Quote from: dukester99 on July 01, 2015, 10:43:29 AM

For now we need to get some active connections. Is hosting a nodes what needs to happen?

Quote from: byk on June 28, 2015, 06:42:30 PM

OK. I agree. Let's use that time to agree as a community on what we want with this coin, make a list of changes taht we want and than (in a week or so) ask him if he's willing to be the dev and to do that.

Ok, no connections at all again. I guess we need a node. If someone can steer me in the right direction on what needs to be done I will host a node.

The last known block that everyone agrees on then host a node from that block onwards.

You guys might or might not be aware that the old spots wallets do not have the ability import a blockchain via the normal method of bootstrap.dat. You can verify this by looking into the init.cpp file. In order to "import" a chain with these wallets you need to follow a more complex process of detaching databases and copying over those block files etc which becomes complicated cross operating systems.

The biggest problem with Ecash going forward is to get a wallet up to date. At some point I attempted this to help you guys but the chain gets stuck every 500 blocks. With a chain size of 1m+ it becomes an almost impossible task. There are ways around it with scripts but a person has to baby sit the process. I was willing to do it and got halfway before I realised during testing that creating a cross-platform compatible up to date bootstrap.dat is going to serve no purpose as the wallet does not have the ability to read it so I halted the effort. It is trivial to create a Linux VPS sync node and at that point I created one to see if it will sync better but the problem is to get an up to date chain on it. A normal chain sync from scratch on a VPS sync node suffers from the exactly same chain-getting-stuck-while syncing symptom than a normal wallet on a PC.

The way out of this for you guys imo is to do the following:
- Have an up to date block explorer (good luck) and export a snapshot of all addresses and the coins in them.
- Choose or create a new wallet, do a premine on block 1 of a balance equal to the Ecash balance less a bunch of zeros and let someone do the swap for you privately by proving ownership of the old address.

Just make sure this time that the new wallet can import a bootstrap.dat in order to easily sort out issues in future.

Not true, just detach database at shutdown from a synced node to get transferable blk .dat files