Quote from: AidBit on July 28, 2014, 04:33:17 PM

Quote from: HR on July 28, 2014, 04:09:14 PM

Quote from: AidBit on July 28, 2014, 03:29:32 PM

Quote from: HR on July 28, 2014, 03:12:54 PM

Quote from: AidBit on July 28, 2014, 01:02:35 PM

Actually, we've changed the protocol version and are ignoring the older versions. Unfortunately we're experiencing new forks and we're still investigating what is going on. Master Checkpoint Node is trying hard to keep everything together for now.
You can connect directly to one of our pool nodes.

Code:

#aidbit.conf
connect=maya.aidbit.net
connect=felix.aidbit.net
connect=kei.aidbit.net

This way you'll limit connection to other nodes.

I know it's frustrating, but it's no better on this side.

Regards,

AidBit

I was looking at the Litecoin Wiki looking for something else and came across the -checkpoints switch for the conf file which limits connectivity to only accepting the block chain matching built-in checkpoints.

Master Checkpointing is already operational and should work much better then just built-in checkpoints... Thanks.

I suspected as much . . . I'm still very low on the learning curve . . . trying to learn and be as helpful as possible in exchange . . .

Question: Master Checkpointing is done from the Master Checkpoint Node? Working to keep everything in line?

Question: -checkpoints is done from each individual wallet (that is so configured)? Working only to ensure that that particular wallet is indeed on the correct blockchain?

Yes, correct!

So each miner could "double up" their protection by including the -checkpoints switch in their own conf file?

Also, another question, did you make some changes that went into effect after block 14898?